The parameters in lilo.conf describe where it can find things at the
time lilo (/sbin/lilo, the installer) is run. So /vmlinuz in the debian
lilo.conf is the debian kernel. If you want to install a kernel from
slackware, with lilo run in debian, you must mount the slackware / on a
mount point in the debian fs, and describe in lilo.conf where lilo can
find it. Then run lilo and you should be right. Two separate lilo's
will also work, if you run the installer on each system you want to
install lilo into.
Lawsom
>< Microsoft free environment
This mail client runs on Wine. Your mileage may vary.
On Mon, 17 May 1999, Tom Taylor wrote:
> At 09:25 AM 5/17/99 +0800, you wrote:
> >Dear all,
> >
> >My intention is installing three different OS in a 4.3 SCSI hard disk
> >drive as follow.
> >
> >1. /dev/sda1 FreeBSD 3.1-stable
> >2. /dev/sda2 Debian 2.1 (kernel 2.0.36)
> >3. /dev/sda3 Slackware 3.6 (kernel 2.0.35)
> >4. /dev/sda4 Linux swap for two distributions
> >
> >The current lilo.conf have a problem on booting the last two
> >Linux distributions. This is the content of the lilo.conf.....
> >
> >boot=/dev/sda
> >delay=30
> ># FreeBSD
> >other=/dev/sda1
> >label=freebsd
> >table=/dev/sda
> >read-only
> ># Debian
> >image=/vmlinuz
> >root=/dev/sda2
> >label=debian
> >read-only
> ># Slackware
> >image=/vmlinuz
> >root=/dev/sda3
> >label=slack
> >read-only
> >
> >This lilo.conf brings a problem of booting the same kernel forever,
> >although it is configured two root partitions. I run lilo command at
> >Debian system so that computer loads kernel 2.0.36 (comes with debian)
> >every time, even if I want to Slackware (which comes with 2.0.35). As
> >the result, Slackware cannot initize 2.0.35 modules correctly.
> >
> >My question is how to configure LILO points to different kernels?
> >
> >In my limit knowledge, I have an idea.............
> >At first, I install LILO at the superblock of two Linux partitions.
> >
> ><debian>
> >boot=/dev/sda2
> >root=/dev/sda2
> >image=/vmlinuz
> >label=debian
> >read-only
> >
> ><slackware>
> >boot=/dev/sda3
> >root=/dev/sda3
> >image=/vmlinuz
> >label=slack
> >read-only
> >
> >After then, I install FreeBSD's boot manager in the MBR of this SCSI
> >hard drive. Thus, there are two LILOes as secondary boot loader and
> >they point to different distributions with different kernel.
> >
> >Is this idea correct?
> >
> >Best Regards,
> >Hon-Yu Cheung
> >
> >
>
> Hi:
> What probably would be easier (I'm lazy) would be to have
different names
> for the boot image (ie: vmlinuz-deb, vmlinuz-slack, etc) then:
>
> ><debian>
> >boot=/dev/sda2
> >root=/dev/sda2
> >image=/vmlinuz-deb <<<<<<<< different kernel image for each
bootable
> >label=debian
> >read-only
>
> Good Luck, Tom
>
> P.S. If you have a kernel source, look in the readme file that gets
> uncompressed with it. That explains about multiple versions.
>
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]
