<br><br><br>Jack Byers [EMAIL PROTECTED]
>"Braverman, Rachel" <[EMAIL PROTECTED]>
>I have RH7.1 installed on a system.
> I'm trying to install RH7.2 on a second disk.
> I want to be able to boot from either of the two versions.
> The problem is with the boot partition, that points to 7.1
>installation, and
> will not bring up correctly the 7.2
> Any idea ? Have someone experienced this ?
I haven't done exactly what you are asking about,
but I have run multiboot long ago rhat4.2 and rhat5.2
now running two (or even 3) slightly different versions of 5.2
But I dont have a separate /boot partition,
which is what your main problem seems to be.
So I cant prove that my suggestions here will work but
they might work as is, and at least should help clarify.
my typical lilo.conf for two roofs both rhat, different versions
--------------
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz
label=linux1
root=/dev/sdb1
read-only
image=/redhatnew/boot/vmlinuz
label=linuxnew
root=/dev/sda3
read-only
other=/dev/sda1
label=win95
table=/dev/sda
---------
corresponding lines in fstab:
/dev/sdb1 / ext2 defaults 1 1
/dev/sda1 /win95 vfat defaults 0 0
/dev/sda3 /redhatnew ext2 defaults 1 2
----
You probably have something similar.
this says my first rhatos with label linux1 has
its /boot as part of its rootfs /dev/sdb1 mounted under /
and my 2nd rhatos with label linuxnew has
its / boot as part of its rootfs /dev/sda3 mounted under /redhatnew
so each rhat has a distinctly separate boot directory
Now, as you have evidently experienced,
if we changed this to put in a separate /boot partition,
then this clean separation is upset, and some sort of trouble ensues.
In my setup here, if there were a separate /boot partition,
then the /boot directory for my linux1 would indeed take hold,
for _both_ stanzas.
When trying to use redhatnew,
it would use the _new_ rootfs under /redhatnew
as demanded by the directive 'root=/dev/sda3',
but then it would have the incorrect boot directory,
so would pick up the linux1 kernel etc.
This may be nitpicking the detail of the failure,
and I cant prove this point
bc I havent actually done what I am saying here.
Details of your failure mode for your 7.2 would help clarify.
If I am roughly right here, then all we need to do is get back the
functionality
of two separate /boot directories.
My suggestions:
1) dont use the separate /boot partition,
if this doesnt break lilo or cause other trouble.
This would at least let you check out multiboot
without the /boot partition
2) try using the separate boot partition only for linux1,
and keep the boot directory for linuxnew
under its /rhatnew, ( if that doesnt brklilo).
To do this, name that /boot partition something like /boot1
then inside your linux1 root dir make /boot a link to /boot1
3) if the /boot partition is large enough
to actually hold two boot directories,
then again name that /boot partition /boot1
and do the link for linux1 as in 2)
Now also make a directory /boot2 inside that /boot1 partition
and make the boot directory under redhatnew a link to
/boot1/boot2
None of the above require repartitioning.
If you have enough space in your /boot partition,
you could just repartition it alone into two,
/boot1 and /boot2 each half size of original
then do the links thing for both....
Something along these lines should work
Let me know how it works out,
regards
Jack
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
