Kernel 2.6.7 Non-Event

Volume 7, Issue 125; 14 Jul 2004; last modified 08 Oct 2010

Download, unpack, configure, build, install, run. That’s the way I like it.

We should be taught not to wait for inspiration to start a thing. Action always generates inspiration. Inspiration seldom generates action.

Frank Tibolt

I finally decided to give the 2.6 kernel series a whirl. Partly this was motivated by a desire to try out the new scheduler, which I’ve been told provides better application performance, partly it was out of a desire to move beyond a certain hackish feeling I have about the way I’ve patched Firewire into 2.4, and partly it was well, you know, because it’s there.

Download. Unpack. Configure. Build. Install. Update /boot/grub/menu.list. Reboot. Run. Firewire: yes; PCMCIA: yes; Wifi: yes; USB: yes; Bluetooth: yes. That’s the way, uh-huh, uh-huh, I like it.

I had to do a little shuffling back and forth to get VPN up again, but that was just poor planning on my part (if you need to download something from behind the firewall in order to be able to get through the firewall, you should download it before you reboot into the configuration where you want to install it!)

Then I tinkered a bit and put some things directly into the kernel that I’ve been running as modules under 2.4 (Toshiba laptop support, USB, the driver for the wired ethernet device, and the IDE SCSI stuff for accessing the Firewire drive and the CD-ROM). All painless.

Getting Firewire and wifi working under 2.4 was a real pain the first time. So far, the 2.6 upgrade has been a non-event.