As stated in my last post, my server died several months ago, and I decided to take that unfortunate opportunity to gain some Unix experience by installing FreeBSD on its replacement. Although this server has been installed for several months, the main reason that this weblog has been down is because of multiple configuration issues with FreeBSD that, frankly, I think should have worked Out Of The Box.
A friend of mine who is adamant about FreeBSD told me to name this inevitable post “FreeBSD from a gentoo user’s perspective.” It’s true that my desktop’s distro of choice has been gentoo for several years, but I’m no ricer. I love gentoo because I love portage–the gentoo package manager which is, in fact, a derivative of FreeBSD’s ports package manager. I don’t care much for any package manager that doesn’t give you the option to change compile-time options. Anyway, I’m going to try my best to leave any bias-ness I may have behind me as I work through the multitude of flaws that I encountered with setting up a FreeBSD webserver.
As a gentoo user, I can understand the expected perils of using a system that is designed to have both . . . → Read More: FreeBSD Perils
Well, my old server died (I think the processor fried itself somehow). Due to school workload, I wasn’t able to properly configure a new server until now, thereby this blog has been down for months (and, surprisingly, I’ve actually had people comment about it being down–mostly because they were unable to flame me, though *shrug*).
Anyway, I’ve finally got a new (actually, it’s quite old) rack-mountable server (minus the rack) running FreeBSD as a replacement. Moreover, I’ve changed the theme, so this site had both a different software and hardware look!
My senior year of high school, I was preparing for probably the hardest exam I’d ever have to take: my Anatomy and Physiology final exam. In order to make an A in the class, I had to make >92 on the exam. Our teacher gave us a pool of 500 questions; of those 500 questions, she would pick 100 to make up our exam. So, I set to work on memorizing the answers to those questions backwards and forwards.
Instead of using note cards (writing the question on the front and the answer on the back), I spent just as much work (maybe less) in writing a small PHP script that would import a list of ‘note cards’, prompt me with a random side (front or back) of a random card, hesitate (allow me to think of the answer), give me the answer upon my request, and allow me to mark whether or not I got it correct. At the end of this process (2 prompts (one for each side) * the # of cards = a long ass time), it gives me a list of the ‘note cards’ that I got wrong so that I can re-study them and . . . → Read More: Study Software
I’ve wanted to setup a serious linux-based firewall for my home network for some time now, and I finally got around to it yesterday.
There are TON of linux router distros out there, but instead of spending 8 hours picking & choosing, comparing & contrasting, nitpicking & debating, I asked someone else ;). Two buddies of mine have a similar setup at their homes: one uses Smooth Wall; one uses IPCop. I arbitrarily chose Smooth Wall (after actually setting it up, though, I think IPCop would have been a better choice–c’est la vie.
The installation is supposed to be quite painless, and it was–for the most part. The documentation and install process was intuitive and easy to follow, but it didn’t work OOTB. I probably only had so much difficulty because of hardware issues (fried NICs?) which is by no means Smooth Wall’s fault. Nevertheless, it took ~5 hours of bang-your-head-against-the-table troubleshooting ’till I could finally unhook the monitor & keyboard, shove it in a corner, and get some sleep.
I was also disappointed with two things that didn’t work as I had expected OOTB:
Note: Thermite is a dangerous pyrotechnic mixture. I am not a licensed professional; I am merely a pyrotechnic hobbyist. If you plan on experimenting with thermite, be sure to research safety precautions of making, storing, reacting, and cleaning-up thermite. Also, be sure to check with your local law-enforcement agency to see if thermite is legal in your area.
So, I figured: D-Link is a popular company, they’re not going anywhere, they sell tons of devices, so my chipset is probably well supported in Linux, right? Wrong.
Every now and then, linux crashes (and consequently, hell feels a little cold). I’m not sure how to diagnose the issue, but I’m almost certain it’s a result of some unstable openGL screensaver, some faulty X app, or basically anything but hardened command-line driven applications (which is simply to say: linux is perfectly stable without a GUI).
Anyway, even fewer times than a crash occurs, I sometimes cannot boot my system following the crash due to a corrupt journal on my main, root partition. To fix it, I have to boot to a live-cd (typically my gentoo minimal install CD), and type one simple command that I have scrawled in huge writing, double boxed on a desk pad. I can’t tell you how many times this little command has saved my life.
Today, I ran an `emerge -uDN world`, and mysql kept failing on the ./configure step because it couldn’t properly execute `ps`.
For as long as I can remember, my gentoo box has been unable to run `ps`. Every time I did, I’d get a “No such file or directory” error regarding /lib64/libproc-3.2.6.so
Upon further investigation, I found that an `ls /lib64/libproc*` showed two files:
/lib64/libproc-3.2.7.so /lib64/libproc.so
…so, `ps` was trying to access 3.2.6, and I had 3.2.7. Obviously something was out of whack–probably an environment variable. I tried creating a /lib64/libproc-3.2.6.so symlink back to the /lib64/libproc-3.2.7, but `ps` only failed with a different error.
So, naturally, I figured I would simply unmerge and re-emerge the package. An `emerge –search libproc` reveled only one package: dev-libs/libproccpuinfo. After unmerging and re-emerging this package a dozen times, I fell back to google. Turns out that the REAL package for the libproc.so file is sys-process/procps. When I got the…
!!! ‘sys-process/procps’ is part of your system profile. !!! Unmerging it may be damaging to your system.
>>> Waiting 10 seconds before starting…
…message, I was sure that I’d break my system, but I continued, finished the unmerge, re-emerged the package, crossed my fingers, and . . . → Read More: `ps` fail with sys-process/procps
Alright, I’ve been working on my research paper (an attempt to document the history and differences, and an overall comparison between the Microsoft DirectX API and the SGI OpenGL API), so I’ve been caught in the inevitable wikipedia trap. Here was my path:
