On Friday 21 September 2001 21:14, you wrote:
> Hi,
>
> Thanks, but as I said in my original posting, I have no problem with LILO,
> or adding OSs to LILO.   What I AM having a problem with is figuring out
> how to compile/install a kernel so that I can keep all the mods/deps from
> my current kernel, AND those from the new kernel, in 2 SEPERATE places (if
> it is possible).
>
> Thanks,
> David Charles

Hmmm, well let's think about this a minute.

All booting is done from /boot.
Kernels that boot must be stored in /boot

kernels are numbered by version and build

like vmlinuz-2.2.19-10mdk
or
vmlinuz-2.4.8-24mdk
or 
vmlinuz-2.4.3-20mdk

I have all three in my /boot.  One boots RC1 on /dev/hda9, the others boot 
8.0 on /dev/hda1.

Now modules

They exist in /lib/modules/2.2.19-10mdk, /lib/modules/2.4.3-20mdk on 
/dev/hda1, and /lib/modules/2.4.8-24mdk on /dev/hda9

Now lilo has boot sections for each of these.  Moreover there is a boot that 
aims at vmlinuz and initrd.imd which are merely links and I can link it to 
either one of the kernels booting with /dev/hda1 as /  (I would have to 
change the root= stanza to make that one boot from /dev/hda9)

OK I also have

initrd.img-2.4.8-24mdk
initrd.img-2.4.3-20mdk
initrd.img-2.2.19-10mdk

I made these or the installer made them.  It is rather simple to do, but 
required if for example one system uses ext2 and the other uses XFS.  These 
are the modules loaded without accessing / partition, which may not be 
available.

So your problem reduces to moving the stuff you have compiled (as BzImage) to 
the right named files, making up your own build numbers to guarantee 
uniqueness. And of course to making the rightly named directories for 
/lib/modules.

This is _please note this, you folks who upgraded the kernel_ the case.  Many 
kernels can coexist on your system, with different names, and the bootloader 
or the symbolic links, give you access to _all_ of them.  The moral is, 
_never_ upgrade a kernel, always install it.  It will _not_ replace the old 
kernel on an install, and it _will_ on an update.  Or worse, only part of it 
will install and you have the interesting educational experience of booting 
one kernel with the modules of another; I guarantee this will be an 
eye-opener.


Civileme


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to