On Sun, 23 Aug 1998, Alan Su wrote:
> "Paul M. Foster" wrote (Mon, 24 Aug 1998 01:34:27 -0400 (EDT) ):
> |>
> |>Debs:
> |>
> |>I have two hard drives, partitioned this way:
> |>
> |>/dev/hda1 dos partition
> |>/dev/hda4 Redhat
> |>/dev/hdb2 Debian
> |>
> |>Here's my lilo.conf, sitting on /dev/hda:
> |>
> |>boot=/dev/hda
> |>map=/boot/map
> |>install=/boot/boot.b
> |>prompt
> |>timeout=100
> |>image=/boot/vmlinuz
> |> label=redhat
> |> root=/dev/hda4
> |> read-only
> |>other=/dev/hda2
> |> label=dos
> |> table=/dev/hda
> |>image=/boot/vmlinuz-debian
> |> label=debian
> |> root=/dev/hdb1
> |> read-only
> |>image=/boot/vmlinuz.old
> |> label=old-redhat
> |> root=/dev/hda4
> |> read-only
> |>
> |>As you can see, I have a Debian boot image sitting on the Redhat
> |>partition, which is the only way that lilo will do it. If I change the
> |>debian part to:
> |>
> |>image=/boot/vmlinuz
> |> label=debian
> |> root=/hdb1
>
> so first of all, this is "root=/dev/hdb1", right?
>
Doh! Yes, it should be /dev/hdb1.
<snip>
> so my system is the perfect counterexample. on /dev/hda lives my
> /home partition. /, /usr, /var, *and* swap are all on /dev/hdc. the
> kernel images are on /dev/hdc2 when i run lilo. so i know for a fact
> that such a thing can be done.
>
Well yeah, but you're talking really about one image, if I read you right.
The image lives on /dev/hdc2 and the kernel then mounts your /, /usr,
/var, etc. Right?
> as far as why you get this message, let me see if i got this
> straight. you are running lilo from red hat? if so, where is the
> debian partition mounted when you boot to red hat? if you mount the
> debian partition in red hat somewhere ('mount /dev/hdb1 /mnt'), point
> lilo to that image (change the image line to read
> 'image=/mnt/boot/vmlinuz') and run lilo, it should work.
>
I'll try it, but when lilo runs, that filesystem isn't mounted yet.
> now that i think about it, i think the confusion might be about the
> image line. it doesn't refer to a file in the partition specified in
> the 'root' parameter; it refers to a file in the current filesystem
> world. did that make sense?
>
I think you're right, but that means that if I have two kernel images,
each on different hard drives, I have to make a copy of one to put on the
booting hard drive, so the lilo bootloader can see it when it runs. That's
what I'm trying to avoid.
Paul
