Installing the new kernel

1. Copy the file 7usr/src/linux/arch/i386/boot/bzlmage” from the kernel source tree to the “/boot” directory, and give it an appropriate new name.
[root@deep linux]# cp /usr/src/linux/arch/i386/boot/bzlmage /boot/vmlinuz-kernel.version.number
NOTE: An appropriated or recommended new name is something like vmlinuz-2.2.14, this is important if you want a new rescue floppy or emergency boot floppy using the mkbootdisk program that require some specific needs like for example: vmlinuz-2.2.14 instead of vmlinuz-2.2.14.a
Copy the file 7usr/src/linux/System.nnap” from the kernel source tree to the “/boot”
directory, and give it an appropriate new name.
[root@deep linux]# cp /usr/src/linux/System.map /boot/System.map-kernel.version.number
3. Move into the “/boot” directory and rebuild the links vmlinuz and System.map with the
following commands:
[root@deep linux]# cd /boot
[root@deep /boot]# In -fe vmlinuz-kernel.version.number vmlinuz
[root@deep /boot]# In -fe System.map-kernel.version.number System.map
We must rebuild the links of “vmlinuz” and “System.map” to point them to the new kernel version installed. Without the new links LILO program will look by default for the old version of your Linux kernel.
4. Remove obsolete and unnecessary files under the “/boot” directory to make space:
[root@deep /boot]# rm -f module-info [root@deep /boot]# rm -f initrd-2.2.xx.img
The “module-info” link point to the old modules directory of your original kernel. Since we have installed a brand new kernel, we don’t need to keep this broken link. The “initrd-2.2.xx” is a file that contains an initial RAM disk image that serves as a system before the disk is available. This file is only available and is installed from the Linux setup installation if your system has a SCSI adapter present. If we use and have a SCSI system, the driver now will be incorporated into our new Linux kernel since we have build a monolithic kernel, so we can remove this file (initrd-2.2.xx.img) safely.
5. Create a new Linux kernel directory that will handle all header files related to Linux kernel for future compilation of other programs on your system.
Recall, we had created three symlinks under the 7usr/include” directory that point to the Linux kernel to be able to compile it without receiving error and also be able to compile future programs. The 7usr/include” directory” is where all header files of your Linux system are kept for reference and dependencies when you compile and install new programs. The asm, linux, and scsi links are used when program need to know some functions from compile-time specific to the kernel installed on your system. Programs call other headers in the “include” directory when they must know specific information, dependencies, etc of your system.
[root@deep /]# mkdir -p /usr/src/linux-2.2.14/include
[root@deep /]# cp -r/usr/src/linux/include/asm-generic /usr/src/linux-2.2.14/include
[root@deep /]# cp -r/usr/src/linux/include/asm-i386 /usr/src/linux-2.2.14/include
[root@deep /]# cp -r/usr/src/linux/include/linux /usr/src/linux-2.2.14/include
[root@deep /]# cp -r/usr/src/linux/include/net/usr/src/linux-2.2.14/include
[root@deep /]# cp -r/usr/src/linux/include/video /usr/src/linux-2.2.14/include
[root@deep /]# cp -r/usr/src/linux/include/scsi /usr/src/linux-2.2.14/include
[root@deep /]# rm -rf/usr/src/linux
[root@deep /]# cd /usr/src
[root@deep src]# In -s /usr/src/linux-2.2.14 linux

Страниц: 1 2