Tag Archives: upgrade

Ubuntu Adventure

I’m not sure what made today different than any other day. Maybe it started yesterday, in the evening, as I fiddled with the bike. I didn’t do much – just some handlebar adjustments and bleed the rear brake. But it felt good to have a wrench in my hand, something I do less of in the winter. I guess the feeling spilled over into today.

So I burned a Ubuntu 7.10 desktop install CD, hauled one of the old laptops – an HP ze5170 – up from the basement and booted XP on it one last time – just to make sure it still worked. It was destined to get a new lease on life!

I began by yanking the rug out from under Windows and booting from the newly burned CD. It liked the display and keyboard as well as the native pointing device, a Synaptics touchpad. I started the installer and went to hunt up an Ethernet cable. I cabled it to the network. I read the Release Notes. No showstoppers there so I pressed on. I was surprised to find the default location selected was acceptable – New York. Had it figured that out from my network or was it coincidence?

Using my personal laptop I logged onto my DHCP server and found that the target box had acquired an IP address and called itself ‘ubuntu’. I saw that a bit of network configuration would be necessary later on. Machines here get named for life, so this one would need its old name and IP. Eventually I would – I hope – configure the old PCMCIA wireless card, but for now the cable would suffice. I turned to the install.

I decided take the guided entire disk option and banish Windows once and for all. I set my name, my login name and password, and chose the machine name. Ooh, what’s this Advanced button on the confirmation screen? Oh, just the boot loader stuff and a survey checkbox. Maybe later. Let’s get the show on the road!

This is a good time to talk a little about what I’d like to ultimately accomplish. I want some kind of Linux running native on the hardware. And some kind of virtual environment – probably VMware – with XP installed, for those times when I need to use Windows. After all, I’ve got quite an investment in good Windows-based software… And run the whole ball of wax with one of those encryption packages that encrypts the entire disk. If I accomplish all that, then I’ll invest in a new battery and use this as my travel laptop for visiting clients and stuff like that. My personal laptop is overkill for that job, the 10 lb desktop replacement that it is. But if this experiment goes well I may just cut over to something like this full-time…

Since presumably laptop would need to boot the new install it seemed like a good time to prepare the network. Ah, I see that there’s a new rev of router software to deal with at some point, too. I thought for a minute that I’d be surprised by a lack of need for a restart. But no, there it was. The elapsed time? Twenty minutes from jamming in the install CD. Not too shabby.

The install CD wouldn’t eject, perhaps because it’s running the OS from the CD now? Yup, that was it. The blank screen during the restart was a little unnerving and seemed to take a while. I checked the network from my personal laptop and watched the DHCP sever hand out its new address. Turning back to the still-blank screen, I poked at the keyboard and the screen came to life.

Holy guacamole! There were 196 updates to be made. I’d be damned if I’d bother to examine each one, just do ’em, dammit. And I went to the kitchen and put on another pot of coffee, the second of the day. The quarter gig of updates downloaded fairly quickly. The updater kicked into the install phase and warned, “[…] this can take some time.” And it did. Another twenty-five minutes in total. And then it wanted another restart, which was a little disappointing. Windows does that when you look crooked at it. I was hoping for more, er, less. Well, there were quite a few updates, and it had been a fresh install.

The blank screen while restarting was still unnerving. And again it took a while. I wondered which boots faster, this or Windows? This was three minutes, clock time, to a login prompt, and another three-quarters of a minute to the desktop.

Thus began a couple of fun hours of messing around with Ubuntu 7.10. I didn’t get very far trying to connect to the network printer. I didn’t get too far configuring the wireless card; driver issues, it looked like. It talked nice to a USB thumb drive collecting dust on my desk, but didn’t play the AVI file on it all the way through without losing audio and getting choppy. It still boots slowly, really, on par with XP on that box if I recall correctly, maybe a little slower. And hibernation, an obvious thing to attempt, made for some really interesting looking (but quite useless) stuff on the screen when it attempted to come back to life. The only sign of life besides that and the running the fan was the caps-lock indicator blinking.

I noted my login credentials for future reference, shut it down properly, stuffed it back into the carry-case, shuttled it back to the stack of stuff in the basement. For a rainy day, I figured. It had been a pleasant diversion, but there was real work yet to do.

Hosting Changes

A host is a host,
From coast to coast
And nobody talks to a host that’s close,
Unless the host that isn’t close
Is busy, hung, or dead.

My goodness, that’s so old it farts dust! Well, timeoff.org has changed hosts and it looks like everything’s running okay again. DNS is an odd beast. I can remember, way back in the dark ages, when change propagation actually did take the week or so that they say it could. The last time I made DNS changes, just a couple of weeks ago, my home ISP seemed to pick up on it in a blistering hour and a half. I had asked friends from around the world (what a small village we live in, eh?) to tell me when they noticed the change and, yep, it was prety snappy. But this time it seemed to take some days. So if you’ve noticed some instability lately, that’s why.

Once I get all of the administrivia out of the way and finish mopping up, I plan to write a little about why this latest set of changes was necessary. It was an odd, unexpected set of circumstances, at least to me, and there just might be some lessons to learn.

A Question of Lubrication

My garage door had been making a little extra noise and seemed to be moving just a little bit slower lately. I did what anyone would do – I checked the log and found that I had neglected my lubrication duties! So I pulled on a pair of latex gloves, grabbed an old towel for the inevitable mess and went to work. I mopped up the old grease from the tracks – the towel collected the gobs of gritty goop nicely. I shot the rollers and the chain with fresh lithium grease. I ran the mechanism several times, paying attention that I’d gotten the grease into all of the moving parts. It appeared that over the years the chain had stretched some and I wondered briefly when it would fail…

And suddenly it stopped, mid-cycle! What’s more, I think I saw wisps of smoke curling from within the motor power head’s housing. Smelled like… and I would later confirm… eau-de-silicon. More precisely, the motor’s startup capacitor was had fried.

Stanley, the manufacturer of the unit, stopped making garage door openers back in the late 90s, the Web told me. Not much chance of finding replacement parts.

Continue reading A Question of Lubrication