On Saturday 01 November 2003 1:44 pm, HaywireMac wrote: > On Sat, 01 Nov 2003 17:41:49 +1100 > > Charlie <[EMAIL PROTECTED]> uttered: > > I usually compile any new kernels in the /home/charlie directory where > > I can access and boot from them even after a newer version install, as > > I don't ever upgrade. In this way the Mandrake kernel that comes with > > the new version install is in the system and by manually adding the > > new kernel to /etc/lilo.conf > > So even if I compile the custom kernel in /home, I can add an entry to > /etc/lilo.conf pointing to it there? That is waaaaay cool.
I do it like this too. The kernel is actually in /boot, as the kernel image you create when you compile. It doesn't matter where the source is- it just serves as the source for compiling the actual kernel image, and the modules, which you install into /boot and /lib, respectively, after you SU to root after the "make modules" stage. Then you do make modules_install, and copy over the kernel image to /boot (naming it whatever), and edit lilo or grub accordingly. This way, there is no messing with a symlink, and everything is complete isolated from your original stock kernel. In other words, once you compile the actual kernel and modules, the huge source directory is of no importance. Only if you need to recompile for some reason, does it come back into play. I still don't understand why some find a need to compile kernels in /usr/src, as root. If there is an advantage to doing so, I'd like to know about it. For me, the other method is far simpler, and serves all my needs with multiple kernels. Robert Crawford
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
