Xavier Toth wrote:
I want to dual boot FC4 and Rawhide . So far I've added a second disk
to my system
which I recently upgraded to FC4. I actually disconnected the original
disk and installed FC4 on the new one letting the installer partition
the disk. Now I've reconnected the original disk and am trying to
configure grub to allow me to boot off either disk. I added an entry
to device.map for the new disk (hb1 /dev/sdb) and copied the stuff in
grub.config and changed the titles and root commands (root (hb1,0))
for the new disk. Unfortunately it only ever boots off the original
disk even when I use one of my new titles. This may not have been the
best way to approach this problem any advice would be appreciated.
grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
password --md5
default=0
fallback=2
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title Rawhide (2.6.11-1.1369_FC4smp)
root (hd1,0)
kernel /vmlinuz-2.6.11-1.1369_FC4smp ro root=/dev/VolGroup00/LogVol00
rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4smp.img
title Rawhide (2.6.11-1.1369_FC4)
root (hd1,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4.img
title Fedora Core (2.6.11-1.1369_FC4smp)
root (hd0,0)
kernel /vmlinuz-2.6.11-1.1369_FC4smp ro root=/dev/VolGroup00/LogVol00
rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4smp.img
title Fedora Core (2.6.11-1.1369_FC4)
root (hd0,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4.img
The easiest way to boot many different operating systems is to install a
secondary systems grub into its boot partition. Then from the
installatiion where grub is installed into the master boot record,
chainload the secondary installation in much th same way that foreign
operating systems are booted by grub.
Chainloader ....
After your installation installed in the MBR starts to chainload your
secondary installation, the primary installation is out of the picture
and each controls their own kernel stanza removals and additions. I boot
4 installations this way. (ME, FC3, FC4 and development.)
For the primary installation add to grub.conf something like the below
stanza.
title Development
rootnoverify (hd1,0)
chainloader +1
For the secondary installation, run the below command while booted into
the secondary installation.
grub-install /dev/hdb1
Assuming that your boot partition is located on the first partition of
your secondary drive.
Hopefully this will give you some clues as how to achieve this.
Jim
--
Eat drink and be merry, for tomorrow they may make it illegal.
