Linux 2.6: Go Configure
When we last talked about Linux 2.6 Kernel we left off at giving our new 2.6 kernel a unique name, so we can tell it apart from our other kernels. In this third, and final, salute to the new kernel, we'll get into the gnarly part configuration (and we'll also cover patching kernels, so you'll know how to keep your new kernels up-to-date).
Configuration is the most tedious, time-consuming part of the process. Howerver, it's extremely important, so don't gloss over it. If you leave things out, you'll have to go through all this again.
Before we leap into the fun stuff, we need to review a couple of items from Part 1 of our trilogy. Remember the command for unpacking the compressed kernel archive:
$ bzcat linux-2.6.3.tar.bz2 | tar -xvf -
Yes, this is the olden way, as a kind reader pointed out. Use it if you have an elderly tar that does not support bzip2 archives. Modern editions of tar support bzip2 directly. The modern way:
$ tar xvjf linux-2.6.3.tar.bz2
Part 1 says to use gcc 2.95.3. I have received reports of using gcc versions up to 3.3 successfully. Your mileage may vary.
The Steps So Far
- Obtain kernel source code, and download it into ~/src
- Make sure gcc, GNU make, binutils, util-linux, and module-init-tools are up-to-date
- Make hard copies of dmesg, lscpi, and lsusb
- Backup any existing .config file (there may not be one)
- Run make mrproper to restore the source directory to a pristine state
- Edit ../linux-2.6.3/Makefile to give the new kernel a unique name, like EXTRAVERSION =new-name
$ lsusb -v | lpr
lsusb is part of usbutils.
This is the most tedious, time-consuming part. Howerver, it's extremely important, so don't gloss over it. If you leave things out, you'll have to go through all this again. It is tempting to recycle your 2.4 .config, and run make oldconfig, but don't. The 2.4 and 2.6 kernels are quite different; this is asking for trouble.
This article was originally published on CrossNodes.