Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 241 — #267

The Linux Kernel

Note

To avoid unexpected effects, make sure that modules whose

functionalities may now have been directly compiled into the

kernel are removed from /lib/modules/<version>/. This is

one of the reasons why inexperienced users are strongly discour-

aged from compiling the kernel.

Note

I x86

To enable GRUB or LILO to boot the old kernel (now /boot/vmlinuz.

old), add an image entry with the label Linux.old in your /boot/

grub/menu.lst or /etc/lilo.conf This procedure is described in

detail in Chapter 8 on page 203. If you are using LILO as the boot loader,

LILO must be reinstalled after modiﬁcations to /etc/lilo.conf with the

command lilo. GRUB does not need to be reinstalled. J

I x86

The ﬁle /boot/System.map contains kernel symbols required by the

modules to ensure successful launching of kernel functions. This ﬁle de-

pends on the current kernel. Therefore, once you have compiled and in-

stalled the kernel, copy /usr/src/linux/System.map to the directory

(/boot/). This ﬁle is regenerated each time the kernel is recompiled. If you

create your kernel using make bzlilo or make zlilo, this is done for you

automatically. If you get an error message like "System.map does not match

current kernel", System.map probably has not been copied. J

9.8 Cleaning Your Hard Disk after

Compilation

If you are low on hard disk space, delete the object ﬁles generated during

kernel compilation using make clean in the /usr/src/linux/ directory.

If you have plenty of disk space and plan to reconﬁgure the kernel on a reg-

ular basis, you might want to skip this. Recompiling the kernel is consider-

ably faster then, because only the parts affected by changes will actually be

recompiled.

241SUSE LINUX Enterprise Server