Jun 11

I’ve been happily running Debian on my ThinkPad for over a year, probably the longest time I’ve ever kept a single OS on the thing. Or rather, I had been until Saturday. Saturday is when I decided to update my X.org.

I’d had some problems with X.org before. Debian Testing upgraded to X.org 7.0, and it turned out the ATI FireGL T2 drivers in that were broken. So, no fancy new X.org 7 for me until 7.1, I thought, which was a shame because the new ATI drivers in 7.x provide full hardware acceleration, including 3D.

Still, updates were to be had, so I went ahead with what I expected to be a routine point release upgrade of 6.9. However, it turned out that the packaging of X.org has been rearranged, along with the system directories.

Result: no X.

I tried running the autoconfig, which has always worked in the past. It didn’t work, couldn’t find the perfectly ordinary USB mouse either. I upgraded everything else via apt-get upgrade and rebooted, and discovered a ton of errors now appeared during boot. I spent an hour or so dicking around before coming to the conclusion that the system was hosed in a way which would probably require some kind of reinstallation.

This isn’t my first moment of dissatisfaction with Debian. PAM was broken for months, I’m not sure if it has even been fixed yet. Sound stopped working a couple of months ago. It seems as if somehow along the way ‘testing’ has become ‘unstable’. Perhaps it’s because of the pressure to speed up the release cycle–but then, I don’t see any new stable releases on the horizon.

So, it was time to weigh options. Debian Testing had just burned me badly, so that was out. I could stick with Debian, reinstall Sarge, and live with no accelerated graphics until the next Debian release, which could be years away. I could try the IBM Linux image, which is based on a well-known commercial Linux distribution that I’m not a big fan of. Or, I could try something else.

The new distribution all the cool kids are running is Ubuntu, so I downloaded and burned a CD and booted it. All the ThinkPad hardware worked first time, including Bluetooth, ATI graphics with 3D acceleration, sound, and ACPI power control. So, it looked as though Ubuntu would give me the Debian base I liked, with the advantage of a release schedule measured in months rather than years, and accelerated graphics.

However, Ubuntu is based on GNOME, and I’ve been a KDE user in recent years. There’s a KDE-based Ubuntu variant (Kubuntu), and also one that runs the XFce windowing environment (Xubuntu). I tried all three.

GNOME is nice and simple in appearance, but it’s a terrible RAM hog. KDE has chronic optionitis, but has lots of handy programs; but I thought about the programs I run all the time, and realized that only one is actually built for KDE–the others are all GTK-based.

Then I tried XFce, which is GTK-based, and noted that I could run XFce and Firefox together and use less RAM than just the KDE desktop. So, XFce was ahead. When I noticed that XFce showed file sizes correctly but GNOME didn’t, the deal was sealed.

Next problem was to back up all my user data. I went on a cleaning out spree, burnt a DVD of old stuff I hope never to need again, and shrunk everything down to under 30GB. I used rsync to back it all up to our MP3 and e-mail server temporarily.

Then, I decided to be daring, and used resize_reiserfs and GNOME partition editor to make space for a new root partition, turning the old partition into /home. This allowed me to install Xubuntu without wiping my home directory.

I just finished confirming that I can get the VPN working, so I don’t have to go into the office in the morning. I’ll get Eclipse and all the other work stuff going again tomorrow.

Oct 24

If you run Debian testing, you might be getting an error like this:

W: GPG error: http://debian.teleglobe.net stable/non-US Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY B629A24C38C6029A
W: GPG error: http://debian.teleglobe.net testing/non-US Release: The followingsignatures couldn’t be verified because the public key is not available: NO_PUBKEY B629A24C38C6029A

The solution is:

# apt-key add /usr/share/keyrings/debian-role-keys.gpg

[Update: If you don't have that gpg file, you need to apt-get install debian-keyring first.]

The cause is apparently that APT 0.6 has made its way into testing. Either there’s now a new key or the new version of APT somehow borks the old keyring or something. I just wanted the solution.

Also, don’t upgrade PAM in Debian testing if you have it configured to count login attempts via pam_tally.so, as a bug in PAM 0.79-3 I hit yesterday causes every authentication to segfault if you use pam_tally.so deny=N, locking you out of your system. The maintainer is working on a fix, the workaround is to comment out your account line for pam_tally.so in /etc/pam.d/*

I guess now that the 3.1 release finally happened, people are getting more relaxed about releasing stuff into testing.

(Noting this here because when I searched for the answer to the APT problem I found a lot of wrong answers before I found the right one. Pagerank hath its privileges.)

Jun 06
  • Red Sox win World Series. Twice.
  • Debian project releases ‘Sarge’.
  • Apple switches to x86. (Get your badge now!)
  • Microsoft switches to PowerPC for Xbox, picks Macs as development systems.
  • Deep Throat confesses.
  • Labour wins third UK General Election in a row.
  • Mathew learns to drive car, moves to Texas.

Coming soon:

  • Showers of frogs.
  • Duke Nukem Forever ships.
  • Pope dies, replaced by Dalai Lama.
  • Passport replaced by RFID embedded in hand.
  • George W. Bush admits mistake, apologizes.
May 10

My first non-bugfix contribution to Linux has appeared in Debian unstable. It’s a data file of disclaimers for the fortune program.

I created it because at work, we’re required to put a paragraph-long legal notice in the login sequence of every machine, informing people that the machine must only be used by authorized individuals, may not be used for confidential material, etc etc.

So now I add fortune disclaimer to my .bashrc, so the disclaimer seems to finish off with something like “Cape does not enable wearer to fly”, or “If rash develops, discontinue use.”

Hey, if I have to look at the thing every time I log in, I may as well get a laugh out of its context.

Aug 14

I’ve switched my ThinkPad to Debian, along with my desktop machine. I did it to get off the upgrade treadmill. I was using a well-known Linux distribution, as customized for IBM use, but a second forced reinstall in under a year made me snap.

I don’t want to reinstall my OS. I don’t mind it so much with OS X, because Apple make it such a trivial task—you archive and install, and your user data and applications stay there, along with all the necessary configuration, and the new OS is installed cleanly. But a RedHat or SuSE reinstall is painful, even if you are smart enough to record what was installed and take copies of the various key configuration files. Frankly, if I didn’t mind reinstalling everything from scratch once a year, I’d run Windows.

So, it was time to move to a Linux distribution that wasn’t going to force me to do unnecessary work. While I like Gentoo, I’d tried and failed to get IBM’s stupid proprietary VPN solution to work with it. So, Debian was the obvious choice.

I’d tried and failed to install Debian before, dealing with that ugly jigdo thing to try and assemble a couple of CDs, only to have the installer bury me in “Hello, you’ve just installed Package Z, here’s a page of useless information…” dialog screens.

Fortunately, Debian now has an actual installer. You download the ISO and burn it on a dinky little 8cm CD, boot it, and it leads you through the process with very little fuss. In fact, for the desktop box the most difficult part was partitioning.

For the ThinkPad, things were a little more exciting. Laptops are almost always packed full of flaky proprietary hardware, and in this case the graphics card was the tough part. Still, I eventually tracked down a working XF86Config-4, polished it up a bit, and was done.

Getting Notes 6 to run was trickier. I ended up using a vintage WINE from November 2003, converted from RPM format via alien, because current releases of WINE are broken in an irritating manner—they cause every scrollable window in the Notes client to be drawn with a double set of scroll bars.

The VPN setup was ugly, involving kernel patches, but I had some instructions from an internal web site which I managed to decipher, and now I can patch and run future 2.6.x kernel releases. I needed to build a custom kernel anyway, as the ThinkPad needed some kernel modules to work fully. As you might guess from the mention of 2.6 kernels, I’m running a ‘testing’ Debian install with a few bits of ‘unstable’ as necessary (basically Mozilla).

So now it’s all up and running, I can ignore the daily Windows virus alerts, and I can keep up-to-date with security patches and OS improvements without spending any significant amount of time doing so, and I can get on with my actual job. Fancy that!

Mar 03

I got jigdo running, and downloaded the first two Debian CDs. Successfully installed this time. Somehow it skipped installing the ethernet drivers, and when I tried adding them with dselect inside Gnome or KDE dselect couldn’t see the CD-ROM.

So, I booted in “emergency” mode, and dselect could then see the CD-ROM. Installed etherconf, ran it, it did everything automatically, rebooted one more time, and the machine is on the net.

Sound still doesn’t work, but I’ll worry about that later.

Now I have some annoying program asking me what network configuration I’d like to use every time the machine starts up, where the correct answer is “no network configuration *you* know about, bucko”; I need to get rid of that…

dselect is definitely way better than RPM.

Feb 28

Today I tried using Debian.

First I tried to find CD images on the internal IBM mirror of the Debian servers. No go.

Next I tried the Debian web site. It directed me to use jigdo to assemble a CD set. The jigdo home page was giving me a 404 error, so I gave up on that option. (It seems to be back now.)

So, next I tried a net install from a minimal CD image. I got past the painful device selection stage, but hit a snag—it demanded a static IP address, with no option for using DHCP. I gave it a 192.168.x.x address and continued. It gave me a blue screen with a cursor near the bottom left, and did nothing for about ten minutes. No disk activity, no network activity.

So I gave up, rebooted, and reinstalled RedHat.

Sorry, Debian, but if I can’t work out how to install you, I’m not going to inflict you on my parents.