Long weekend here at Damage Labs, as I worked on several different projects. The late days of last week and part of Saturday were spent banging away on a Linux box trying to get everything configured right. This was concentrated, hard-core Linux setup like I hadn't done in quite a while. Although it was, of course, difficult and somewhat tedious, the computing was surprisingly painless. I enjoy a computing challenge when reasonable progress happens somewhat regularly. When you're deep into compiling and configuring a *nix system, good things are possible. You can have one of those sessions where time just melts away, and when you emerge some time later, much has been accomplished. That can be pretty rewarding. I may forget how I did it all six months from now, because I don't visit Linux config-land often enough, but for now, I'm happy and the work is done.

Later Saturday and most of today (Sunday), though, was difficult. The Linux part was over, and I was back to setting up test systems. Today, especially, was a Bad Computing Day. Ever had one of those? Sometimes, you're just better off putting down the screwdriver, closing down the install programs, and going outside or something. I damn near fried an SFF system, or at least it seemed so for a good 20 or 30 minutes there when I couldn't get it to come back to life. Then I got it booting again, but... well, wait for the review. Heh. On another box, I discovered a pair of registered DDR400 DIMMs¬óCAS 2, no less¬ówon't boot at anything but 333MHz. (These Opteron/FX motherboards don't offer lock-it-down manual control over RAM clock speeds. I suppose I need to have a look into the SPD to confirm this RAM isn't just the wrong type.) Anyhow, bizarre stuff, as is typical on a Bad Computing Day.

Regardless, actual articles will come out of these projects. With luck, we'll have one or two of them soon, so stay tuned.

Tip: You can use the A/Z keys to walk threads.
View options

This discussion is now closed.