Sorry for the repeat, the redhat digest evidently cutoff last half
of full reply
Here it is again, with a few more comments hopefully clarifying
just how I set up multiple RH on different disks.
Dave Reed wrote:
>I eventually just decided to trust the floppy boot disk wouldn't go
>bad (I have never found floppy disks to be that reliable) and just
>tried it.
>Fortunately, it worked fine. I'm not certain how lilo figures out
>where /boot is when it's on a different partition than /
> (in the first image, /boot is on /dev/hdc1 and / is on /dev/hdc2).
>Here it is for anyone who is curious:
>boot=/dev/hda
>map=/boot/map
>install=/boot/boot.b
>prompt
>timeout=50
>default=linux
>image=/boot/vmlinuz-2.2.14
> label=linux
> read-only
> root=/dev/hdc2
>image=/boot/vmlinuz-2.2.12-20
> label=linux-6.1-orig
> initrd=/boot/initrd-2.2.12-20.img
> read-only
> root=/dev/hdc2
>image=/boot/vmlinuz-2.2.14
> label=rh52
> root=/dev/hda3 read-only
>other=/dev/hda1
> label=win95
> table=/dev/hda
--------------------
First of all,
just how lilo does its magic when /boot is ona different disk
is not something I am going to try and explain, Ijust know it works.
How that works is independent of the problem you are asking about,
setting up two rhat root filesytems.
Of course everything lilo needs has to be available to it,
and that means it has to be mounted somewhere.
If you understand how lilo does it when just doing one rootfs
then there really isnt any difference when doing multiple rootfs.
Second, for the multiple rootfs,
you again have to keep in mind that everything lilo needs
must be mounted somewhere.
You can have one and only one rootfs mounted as /.
So your to-be-added rootfs has to be mounted somewhere else.
That is achieved either by fstab or by a manual mount command.
Lilo knows where to look by the two different "root = " directives
in your two different stanzas.
I would change your above to following /pair/ of lilo.conf
(I don't show your preamble, the 6.1-orig stanza, or the win95 stanza)
1)for use when booted up in rh6.1
image=/boot/vmlinuz-2.2.14
label=linux
read-only
root=/dev/hdc2 ### /dev/hdc2 is mounted on /
image=/rh5.2/boot/vmlinuz-2.2.14
### /rh5.2 is where redhat5.2 rootfs is mounted when bootedin rhat6.1
label=rh52
root=/dev/hda3 ### /dev/hda3 is mounted on /rh5.2
read-only
-----
2)for use when booted up in rh5.2
image=/rh6.1/boot/vmlinuz-2.2.14
### /rh6.1 is where redhat6.1 rootfs is mounted when bootedin rhat5.2
label=linux
read-only
root=/dev/hdc2 ### /dev/hdc2 is mounted on /rh6.1
image=/boot/vmlinuz-2.2.14
label=rh52
root=/dev/hda3 ### /dev/hda3 is mounted on /
read-only
----
this type of dual rootfs setup works for me,
in my case two versions of redhat5.2
for one of my rootfs /boot resides outside of /, similar to your case
and no trouble results.
I don't need to use a bootfloppy
lilo can be run (if necessary) when booted up in either 5.2 or 6.1
In this method I do have to keep parallel lilo.conf
and two parallel fstab
one under /rh6.1/etc and the other under /rh5.2/etc
but this is not hard to keep consistent with any future changes.
at any give time
one or the other of the two rootfs is mounted as /
with the other mounted under a directory with its identifying label.
once working,
the rootfs that isn't being used as /
doesnt have to be mounted at all,
unless you want it mounted to be accessible for examination
or wanting to rerun lilo ...
this way that other rootfs has some degree of protection
regards
Jack
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
