Linked by Ben Hughes on Tue 5th Oct 2004 19:16 UTC
GNU/Linux, and all other operating systems, are based around a kernel which controls hardware access and maximizes CPU and RAM efficiency by controlling when and how much programs get to use. The difference between Linux and most other operating systems (closed source ones at least BSD and other open source OS's you can do this with) is that you can compile the kernel to meet your needs.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
For a correct kernel rebuilding procedure search google. If you can't find anything go to:
http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html
The safest way to make sure you don't "f00barred your system"
(who writes this crap anyway!?) ALWAYS leave and do not OVERWRITE your default kernel (and relevant lilo entries).
make mrproper (first time, and then only to reset values)
make menuconfig (or xconfig)
make dep
make clean
make bzImage
make modules
make modules_install
make install
lilo <- don't forget it
"make install" moves all the newly created files to the correct places, and also updates lilo with a new entry to reflect the newly created kernel. If you use grub I think you have to add the entry manually.
Adding -jx (where x>3) flag to "make" greatly improves compilation times on HT and/or SMP systems. On my 2x3.4 Xeon (oc), 2G, I don't have enough time to boil an egg durring the entire compilation process.