Before you do anything else, make sure you have a way to boot the OS.\u00a0 Make a bootdisk and test it.<\/p>\n
Get the source for the kernel and put it in \/usr\/src<\/tt>.
\ncd \/usr\/src<\/tt>
\ntar -xzf <kernel source file name><\/tt>
\nThe kernel source lives in \/usr\/src\/linux<\/tt>.\u00a0 Linux is usually a symbolic link to the source tree.\u00a0 ls -l<\/tt> will show this.\u00a0 You can’t get into too much trouble here, but it can get kind of untidy if you don’t do this right. If you are upgrading, copy the .config file from your old Linux source tree to the new one, and type make oldconfig<\/tt>
\nFrom X Windows, type make xconfig<\/tt>
\nFrom a console, type make config<\/tt> or make menuconfig<\/tt>
\nSelect your options and save the configuration.\u00a0 The configuration is saved in the file .config<\/tt> in \/usr\/src\/linux<\/tt>.\u00a0 You might want to copy this to a floppy or something.
\nOur sequence from here is:
\nmake dep<\/tt>
\nmake clean<\/tt>
\nmake bzImage<\/tt>
\nmake modules<\/tt>
\nmake modules_install<\/tt>
\nmake bzdisk<\/tt><\/tt><\/p>\n
This sequence will compile the kernel and modules.\u00a0 For the last command, make sure you have a blank floppy in the drive so you can copy the kernel to it. If you like you can type:
\nmake dep clean bzImage modules modules_install<\/tt><\/p>\n
Copy System.map (\/usr\/src\/linux\/System.map) and the kernel (\/usr\/src\/linux\/arch\/i386\/boot\/bzImage) to \/boot (or wherever your lilo.conf file points to). And make sure your symbolic links are OK. We (as well as most) make a symbolic link:
\nln -s vmlinuz-2.4.1 vmlinuz<\/tt>
\nln -s System.map-2.4.1 System.map<\/tt>
\nWe then can leave our lilo.conf file pointing at \/boot\/vmlinuz. It is also wise to copy the image section in lilo.conf and create another label, linuxold for example, and use the previous known good kernel as the image. When you reboot, you can select the old kernel if you have problems with the new one. After you are done editing lilo.conf, run \/sbin\/lilo<\/b>. If there are problems with your configuration, links, etc., the output of lilo may clue you in. After you have run lilo, reboot your system and type dmesg | less<\/tt> to check out how your kernel booted.<\/p>\n","protected":false},"excerpt":{"rendered":"
Before you do anything else, make sure you have a way to boot the OS.\u00a0 Make a bootdisk and test it. Get the source for the kernel and put it in \/usr\/src. cd \/usr\/src tar -xzf <kernel source file name> The kernel source lives in \/usr\/src\/linux.\u00a0 Linux is usually a symbolic link to the source […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"class_list":{"0":"post-52","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-gnu-linux","7":"entry"},"acf":[],"yoast_head":"\n