12.3. Linux-2.6.17.11

Building the kernel involves a few steps—configuration, compilation, and installation. Read the README file in the kernel source tree for alternative methods to the way this book configures the kernel.

The following patch fixes on intialization issue with the tulip network driver:

patch -Np1 -i ../linux-2.6.17.11-tulip-1.patch

The following patch merges changes from Linux-MIPS into the kernel:

patch -Np1 -i ../linux-2.6.17.11-mips-1.patch

The following patch merges updates for Linux-MIPS kernel:

patch -Np1 -i ../linux-2.6.17.11-mips_fixes-1.patch

Prepare for compilation by running the following command:

make mrproper

This ensures that the kernel tree is absolutely clean. The kernel team recommends that this command be issued prior to each kernel compilation. Do not rely on the source tree being clean after un-tarring.

If, in Section 11.7, “Configuring the Linux Console,” it was decided to compile the keymap into the kernel, issue the command below:

loadkeys -m /lib/kbd/keymaps/[path to  keymap] > \
    drivers/char/defkeymap.c

For example, if using a Dutch keyboard, use /lib/kbd/keymaps/i386/qwerty/nl.map.gz.

Configure the kernel via a menu-driven interface. Please note that the udev bootscript requires "rtc" and "tmpfs" to be enabled and built into the kernel, not as modules. BLFS has some information regarding particular kernel configuration requirements of packages outside of CLFS at http://www.linuxfromscratch.org/blfs/view/svn/longindex.html#kernel-config-index:

make menuconfig

If desired, skip kernel configuration by copying the kernel config file, .config, from the host system (assuming it is available) to the root directory of the unpacked kernel sources. However, we do not recommend this option. It is often better to explore all the configuration menus and create the kernel configuration from scratch.

Compile the kernel image and modules:

make

If using kernel modules, an /etc/modprobe.conf file may be needed. Information pertaining to modules and kernel configuration is located in the kernel documentation in the Documentation directory of the kernel sources tree. Also, modprobe.conf(5) may be of interest.

Be very careful when reading other documentation relating to kernel modules because it usually applies to 2.4.x kernels only. As far as we know, kernel configuration issues specific to Hotplug and Udev are not documented. The problem is that Udev will create a device node only if Hotplug or a user-written script inserts the corresponding module into the kernel, and not all modules are detectable by Hotplug. Note that statements like the one below in the /etc/modprobe.conf file do not work with Udev:

alias char-major-XXX some-module

Because of the complications with Udev and modules, we strongly recommend starting with a completely non-modular kernel configuration, especially if this is the first time using Udev.

Install the modules, if the kernel configuration uses them:

make modules_install

After kernel compilation is complete, additional steps are required to complete the installation. Some files need to be copied to the /boot directory.

Issue the following command to install the kernel:

cp vmlinux /boot/vmlinux-2.6.17.11
gzip -9 /boot/vmlinux-2.6.17.11

System.map is a symbol file for the kernel. It maps the function entry points of every function in the kernel API, as well as the addresses of the kernel data structures for the running kernel. Issue the following command to install the map file:

cp System.map /boot/System.map-2.6.17.11

The kernel configuration file .config produced by the make menuconfig step above contains all the configuration selections for the kernel that was just compiled. It is a good idea to keep this file for future reference:

cp .config /boot/config-2.6.17.11

It is important to note that the files in the kernel source directory are not owned by root. Whenever a package is unpacked as user root (like we did inside chroot), the files have the user and group IDs of whatever they were on the packager's computer. This is usually not a problem for any other package to be installed because the source tree is removed after the installation. However, the Linux source tree is often retained for a long time. Because of this, there is a chance that whatever user ID the packager used will be assigned to somebody on the machine. That person would then have write access to the kernel source.

If the kernel source tree is going to retained, run chown -R 0:0 on the linux-2.6.17.11 directory to ensure all files are owned by user root.