In our last episode, I asked “Before I tie myself in knots, is there any particular configuration

that someone might recommend for my Ubuntu box before I start tossing

out Ruby scripts? I’m willing to go so far as to rebuild the whole


As usual, Justin James had some fine configuration advice that put my mind at ease, and I was all ready to start tooling around on the laptop when fkchang

dropped this bomb on me: “This may not help you, but there is a Rubuntu

in works, Ubuntu set up to develop in Ruby.” So far, based on a quick

Google search, Rubuntu appears to still be vaporware, but if anybody

has a lead on an iso for a live CD, I’d love to take a look at it.

Of course, I could do just as well to bang around with Ruby on my

current Ubuntu box, if only to learn some things about Linux the hard

way. Like, say, how to download a tarball and do something with it.

In the meantime, I did confirm that my battery issues were hardware

related. After a software update, Ubuntu was able to read the current

charge state of the battery, and for the first time ran off battery

power. The downside? The battery read as 87% full and could only

sustain the system for about 90 seconds. When I rebooted from AC power,

the battery didn’t read flat, but about 26% full. This matches exactly

what AlanGeek

predicted–the old NiCad cells have a devilishly reduced capacity that

can no longer deliver enough voltage to run the laptop, even when the

cell is “fully charged.”

If anybody has a working spare battery for this unit lying around, I’ll trade it for some TR swag. Seriously. Just ask Palmetto, who got a similar deal with the Wacky Linux Wireless Card.

So, homework for this week, send me a link to a nice tarball extraction

FAQ, and I’ll blog all the embarrassing details of me fumbling at the

command line.