On Sun, 27 Jun 2004 17:56:32 +0000, Rich Grise wrote:

> Well, I've gone and shot myself in the foot again. ISTR reading
> something about a dual-boot system, or at least two different
> kernels, and someone said that they have to have different names.

Erm, well it does help, but its not the only way to skin a cat.

> OK, fair enough.
>
> But, I thought, isn't having them on different partitions enough?

Yes it is but what i see is all kernels are in the same directory or
partition.
You are telling lilo to use the same kernel for all systems, NOT such a
good idea as you have well found out.

> i.e.: Here's the relevant parts of my lilo.conf:
>
> # Start LILO global section
> boot = /dev/hda
> prompt
> timeout = 50
> vga = ext
> image = /boot/vmlinuz
> root = /dev/hdb1
> label = Slack-10.0
> read-only # Non-UMSDOS filesystems should be mounted read-only for
> checking
> other = /dev/hda1
> label = W2K
> table = /dev/hda
> image = /boot/vmlinuz
> root = /dev/hdb8
> label = Slack-9.1
> read-only # Non-UMSDOS filesystems should be mounted read-only for
> checking
> image = /boot/vmlinuz
> root = /dev/hdb7
> label = Boot0
> read-only # Non-UMSDOS filesystems should be mounted read-only for
> checking
> -------------------------
>
> I guess I had assumed that when I pick option 1, it loads vmlinuz from
> /dev/hdb1/boot, option 3, /dev/hdb8/boot, option 4, /dev/hdb7/boot.

Wrong yes you were wrong, however you can do it this way, BUT the kernel
image names _must_ be different and have thier "root device" changed with
the program rdev OR you need to give an 'init' option to lilo.

>
> Obviously, I was wrong, because now, (this lilo.conf was done while in
> 10.0, and written to the MBR) when I select option 3, boot Slack 9.1, it
> loads kernel 2.4.26, which is on /hda1.
>
> Does that mean that lilo itself reads the "image" values before it
> decides which partition to boot from? Like, it can only get it from
> hdb1?

lilo -v -v -v will show you what it does.
Yes 3 times -v

>
> So, I should put:
Nope wrong...
[snip]

I have chaged your lilo.conf to;

image = /boot/vmlinuz-2.4.22
root = /dev/hdb8
label = Slack-9.1
read-only

image = /mnt/boot/vmlinuz-2.4.22
root = /dev/hdb7
label = Boot0
read-only

Mount /dev/hdb7 under mnt and do the folloing.
rdev /mnt/boot/vmlinuz-2.4.22 /dev/hdb7

run lilo with the -t option and make sure there are no errors, if no
errors run without -t to update everything, reboot and you should be on
your way.

If i have missed somethig let me know, i am not perfect today.

>
> Thanks,
> Rich

--
If the Linux community is a bunch of thieves because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/