Don't Call it a Comeback
On June fourth, I was running in the Tourne on a trail I first ran twenty years ago, a trail I've run hundreds if not thousands of times before. On that morning, my foot came down on a wet rock at just the wrong angle, slipped just enough and I rolled my ankle. Not only did I roll the joint, I came down on it with enough force to break it; a fact I would learn when I final saw a doctor about it on June ninth.

No surgery was required, but I was unable to run for three months. I was finally cleared to run. The plan was to start with short distances, about a quarter mile, on a rubberized track then build up from there, moving on to treadmills and eventually roads and trails. I was instructed to spend six months rebuilding my 60 mile per week base.

On the morning of September 11 (a day I will never forget and a morning that will always make me feel a bit uneasy), I took to the track for the first time. I started by walking a mile. As I finished the fourth lap, I said a prayer, asking God to give me the run I needed and the wisdom to know when to stop. I queued up my playlist: AC\DC's "Back in Black" and LL Cool J's "Mama Said Knock You Out." I took my first stride.

I've been progressing well in the last two weeks; pushing it on some days, resting when necessary. Though the short, slow distances have been frustrating, it feel good to be running again. Every stride I take I'm reminded of everything I love about the sport.

It's good to be back.

[/running] [permanent link]

How long does it take to build a linux kernel?
It has been a number of years since I built a linux kernel. Slackware 9.1 was the last GNU/Linux distro I used before switching back to BSD. Tonight I put together a machine from some old parts (1.2GHz celeron with 256KB cache, 256MB RAM, 20GB hard drive) and installed Slackware 12. I customized a kernel configuration and attempted to build it. I don't remember the 2.4 kernel taking as long to build as this 2.6 kernel. It took nearly two hours. Granted, this machine is fairly old, but 2 hours? After I complete the tasks for which I needed this setup, I'm going to install an older Slackware with the 2.4 kernel and build that. I may also install FreeBSD and NetBSD and build their kernels. I'd like to get an idea how long it takes to compile other kernels on this rig.

[/unix] [permanent link]

Duality
Given the infinitesimally small reader base of this weblog, and the fact that most, if not all, of those readers know me personally, there's a good chance that you know I've fairly recently gotten a pair of tattoos.

The first tattoo, on my right arm, is a "26.2" in a giraffe print. That number, of course, is the distance of a Marathon in miles. Approximately one tenth of one percent of the population has ever completed a Marathon. I am one of those individuals and it is because of the Giraffes, the running team my friends started and pulled me into, that I was able to accomplish this feat.

The second tattoo, on my left arm, is a 6x8 grid of binary digits which spell out my first initial and last name in ASCII. Beneath the binary grid is a "v3.1" in a more stylized font. I was named after my father who had been named after his father, making me the third, version 3.0 if you will. In the last few years I've "upgraded." I'm smaller, faster, stronger, kinder, more extroverted and more optimistic than I was, but I am not an entirely new person. Hence v3.1.

There's more to the meaning of these tattoos than the explanations above. They represent the duality of myself. One represents the decidedly geeky nature that has been a part of me for almost my entire life. The other represents a newer aspect of myself, the endurance athlete.

It has been difficult for me to resolve these aspects. You were a nerd or a jock. There was a perceived inherent conflict between the two. You could be one or the other, not both. I was a nerd. I was never a jock. Now I'm both.

And I can be both. There is no reason can't, because this is what I've become; this is what I am.

[/musings/self] [permanent link]

FreeBSD 6.4 EoL
As of yesterday, FreeBSD 6.4, and with it the entire 6.x branch, has reached its End-of-Life. It's time to upgrade (or maybe upgrayedd, for a double dose of something-or-other).

So herein lies the problems. Months (years?) ago, I attempted to upgrade tak to FreeBSD 7.2. I plugged in a SATA disk into my workstation, installed the OS, reconfigured all the daemons, services, and functionalities tak has running, copied over a snapshot of all the data, and then edited the fstab to match the device names as they'd exist on tak.

I removed the IDE root disk and installed the new SATA disk and tak and watched the kernel fail to find the root disk. Or the other SATA disk in tak.

Based on the bug reports in the FreeBSD Gnats system, and various conversations in the mailing list, it seems Asus, who made the motherboard in tak, used a slightly non-standard SATA implementation on this particular board. Between the 6.x and 7.x line, some work had been done on the SATA drivers in FreeBSD and mad them more standards-compliant (a good thing). This, however, broke SATA on this Asus board.

Tak is about 6 years old now, and other than some over heating issues, serves its purpose well. So do upgrade to FreeBSD 8.x on an IDE disk and replace the other SATA disk with another ATA disk, or do I build a new, lower-power, higher-performance system?

If anyone actually reads this, feel free to use the new comments feature to give me feedback. I think it's working.

[/unix] [permanent link]