According to [EMAIL PROTECTED]: While burning my CPU.
> 
> 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.....

As i see it, the last two are the same kernel.
They both have image=/vmlinuz

I have had 4 different installations, redhat, slackware, suse and debian on
2 different drives, /dev/hda and /dev/hdb, to boot then i had all kernels in
/boot which was /dev/hda1 i had 14 different kernels defined in lilo.conf
all located in /boot on /dev/hda1.

>From the above you should see where you are going wrong.

> 
> 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
> 


-- 
Regards Richard.
[EMAIL PROTECTED]

Reply via email to