Time Travel?
A few months ago I happened to snap a photo of the DeLorean on Main Street in Boonton near the Darress Theatre. It's probably one of my favorite photographs of the car and certainly one of the best I've ever taken.
The theatre was built in 1919 and has remained largely unchanged since then. A lot of Boonton still has a very old "look and feel" to it, and this section of Main Street served as a perfect backdrop for the DeLorean.

[/dmc] [permanent link]

Philadelphia
The night before I woke up every hour, looked at the clock, said "I have N hours before I need to get up" and went back to sleep.

I lost a lot of fluids because I couldn't turn the temperature in the room down and spent the night sweating. When I got up I drank a lot of water and GuBrew, but as it turns out, not enough.

The weather was good, about 46 at the start. It was sunny, which was quite a problem when I got a migraine at mile 8. It took me about a mile to get my imitrex out of my pocket and actually take it. At the half I was still close to the 3:20 pacer and I considered taking the turn for the finish line, but decided to keep going.

As the nausea from the migraine subsided, I started getting a stomach cramp. At mile 17 I stopped at medical. After some back and forth the decided the cramp was likely due to dehydration and they made me sit and drink in front of them for 15 to 20 minutes before they cleared me to continue.

After that I went on my way at a much slower pace. At about mile 24 one of my teammates, Tom, caught up to me (this was his 19th race at marathon or greater distance). He paced me and got me through to the end.

I ended up finishing at 3:55:46, far off from my goal. But now I know I can finish the distance so it's just a matter of doing it faster. I'd like to get two more in before New York next November.

Right now, I feel much better than I thought I would. It was weird, when I woke up this morning, I was walking around the hotel room for a half hour feeling just fine. Then I put my shoes on and everything from my feet to my shoulders started hurting. That's more-or-less subsided now, thankfully.

[/running] [permanent link]

Optical Illusion
I saw this today. I thought it was interesting.

[/musings] [permanent link]

WTF?
I'm used to guitarists mocking the bass and bassists. It doesn't bother me too much. But this... This irritated me. A lot.
Today at work there was a group of people talking about Rock Band and Guitar Hero 3. None of them actually know how to play intstruments but they claim to be great at these games. They seem to believe this entitles them mock bassists.

• "Oh man, bass is so easy. It's the guitar that's the hard part. Yeah, I'm on expert on the guitar."
• "Yeah, bass is so stupid."
• "So It's me, my brother, and my sister. I play guitar, he's on drums, and my sister sings."
  "what about bass?"
  "My friend just got Guitar Hero 3. I'll make him play bass."
  [Both laugh]
• After making statements indicating this person believes he actually is better than Tom Morello, "After you make Tom Morello or Slash your bitch, they play bass for you."

[/musings] [permanent link]

chdir(2)
So today at work another developer many years my senior, with many more years experience than I, came to me with a Unixy problem.
"When I have a program, how can I have it so the current working directory for all processes it starts isn't the one that it started in?"
"chdir."
"No, I want so that if this process starts something like ls, when ls stats 'dot' I want 'dot' to be the directory that process wants it to be, not the directory that process was started from."
After about 15 minutes of me suggesting chdir while he said that's not what he wanted but then describing chdir, I finally wrote something along the lines of the following

#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>

int
main (int argc, char *argv[])
{
  system("/bin/pwd");
  system("/bin/ls");
  chdir("/tmp");
  system("/bin/pwd");
  system("/bin/ls");
  chdir("/etc");
  system("/bin/pwd");
  system("/bin/ls");
  chdir("/");
  system("/bin/pwd");
  system("/bin/ls");
  return 0;
}

I compiled that, ran it, showed him the output. He said, "Yeah, that's what I want to do."
I showed him the code.
"chdir does that?"

[/unix] [permanent link]

Alpha
Due to the power failure, there was the loss of several hours of work. Last night I installed FreeBSD 6.2-RELEASE on an old DEC AlphaStation 200 I have. I had started building a new, smaller kernel for it around 23:30 last night. It had not completed by the time of the power outage. I have restarted that build.
Any one reading this would reasonably ask, "Why are you not as confused/angry/annoyed with a compile that was not finished in 7 hours as you were about one that took 3 hours?"
The answer is simple. This AlphaStation is powered by a 100MHz DEC Alpha EV4 CPU and has 64MB of RAM. To the best of my knowledge, DEC made this machine around 1994 or 1995. I expected the build to take a long time; the machine is around a dozen years old.

[/unix] [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]

I Survived Julyapalooza!
My friend had his annual Julyapalooza Barbecue in Brick today. This time I made it through the day without any near-death experiences!

[/musings] [permanent link]