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!
Michael Altfield
Hi, I’m Michael Altfield. I write articles about opsec, privacy, and devops ➡
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:
DHCP DNS VPN Michael Altfield
Hi, I’m Michael Altfield. I write articles about opsec, privacy, and . . . → Read More: Smooth Wall
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.
Michael Altfield
Hi, I’m Michael Altfield. I write articles about opsec, privacy, and devops ➡
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.
Type this to fix an ext3 journal corruption:
e2fsck -b 32786 /dev/sda3
Michael Altfield
Hi, I’m Michael Altfield. I write articles about opsec, privacy, and devops ➡
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:
Michael Altfield
Hi, I’m Michael Altfield. I write articles about opsec, privacy, and devops ➡
So, it turned out that--by some miraculus chance--the day I decide to move my blog from wordpress.com to my own server is the day after a major upgrade of wordpress is released (v2.3 to 2.5). I figured that, while I was at it, I would upgrade the server that I setup a few weeks back (I've been planning this move for a while now, just never really got around to finishing). I'm pretty sure I followed the installation process just fine, but when I tried to go to any page on my fresh, new site (including wp-admin/upgrade.php) I got slammed with this lovely error:
Fatal error: Call to undefined function require_wp_db()
Eventually I decided "fuck the installation instructions." I was able to install it by copying my config file and other data TO the new wordpress folder (the suggested process is the reverse: copying the new files into your current, older install).
It's a bitch of a thing to search, too. If you search for that error (at least now, anyway) you get a bunch of popular blog sites that have since been fixed. There is no info from the webmaster or blog author as to HOW they fixed it, . . . → Read More: Blog Moved & Upgraded
Well, I've been fuming for the past few weeks over something, and I've just now gotten around to doing something about it.
I went back to my dorm room the other day, and a few buddies followed me in. One of them was carrying a camera; he was filming me for whatever reason (he's weird like that). Anyway, I sat down at my computer and unlocked it (brought it out of the screensaver with my password) so I could begin studying for the upcoming finals (the next morning). Soon as I did, the dude with the camera behind me smiled and said, "Now I've got your password." I didn't know what to do. My computer password is the most secure password I have: alpha, numeric, symbol, and 10 characters long. I use that VERY secure password for the things that I REALLY need secured: computer data, and banks. The first former would be bad, but the later would be worse. If he knows that password, he can literally bankrupt me. Oh shit.
So, something had to be done; I needed to evolve the way I secure things. I'm in college now, so I should probably do it anyway. I need . . . → Read More: Grown-up Security
So, I upgraded by laptop (hp tx1000z) from Feisty Fawn (Ubuntu Linux Version 7.04) to Gutsy Gibbon (Ubuntu Linux Version 7.10) today. My results are as follows:
Pros:
Integrated Wireless support for broadcom chips Ubuntu FINALLY has pidgin. It automatically backed up my overwritten config files. The "Leave Message" feature of Gnome 2.20.0
Cons:
The integrated wireless support for my broadcom chip does not work at all. The laptop doesn't boot unless I press the power button after an erorr, then repeatedly tap a key. It killed virtual box (my virtual machine program) My speakers don't produce sound anymore My webcam no longer works My touchscreen isn't working anymore (it's not misconfigured; it's not recognized) Computer starts with infinite >97% CPU usage 30% of the time My computer's screen dims after momentary idle My computer's screen dims after momentary idle after I turn uncheck the "Dim when idle option" My computer turns off after I have the laptop lid closed for a few minutes The computer isn't auto-locked anymore when the lid is closed Pornographic screensaver was installed on my computer
More cons (I separated this list from the other because it's not something that Gutsy broke, but something it . . . → Read More: Gutsy Upgrade
