dual boot fedora 3 and suse 9.1
 

Ok im using the fedora core 3 bootloader and i want to either boot from fedora or suse 9.1 their both on seperate hard drives

heres what my grub.conf looks like

# 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 (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.9-1.667smp)
root (hd1,0)
kernel /vmlinuz-2.6.9-1.667smp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-1.667smp.img
title Fedora Core-up (2.6.9-1.667)
root (hd1,0)
kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-1.667.img



This is What my grub for suse looks like

root (hd0,1)
install --stage2=/boot/grub/stage2 /boot/grub/stage1 d
(hd0) /boot/grub/stage2 0x8000 (hd0,1)/boot/grub/menu.lst

But when i try and combine the 2 i get all kinds of errors with grub


any ideas

Try adding something like this to Fedora's /boot/grub/menu.lst

Thank you soo much
that actually worked im using suse right now

Re: dual boot fedora 3 and suse 9.1
 

This is wrong for SuSE.

This is what I think happened. You installed SuSE, but never successfully booted from that hard disk. It looks like SuSE sets grub up to install itself on the first boot. I have never seen these lines in a SuSE menu.lst before, so I suspect that SuSE changes the file when you boot for the first time (to finish the install). Had you finished the install by booting off SuSE's boot device, the file would have been changed.

I didn't know that "install" could be run from the configuration file. I just checked, and apparently it can. Weird.

yea it is really weird but what someone else posted ^ there it made it so my suse can dual boot with fedora core 3
now is there any way i can add windows back as like a tripple boot?

Where is Windows? If it's on /dev/hda1 (that's where Windows likes to be...)

If your Windows installation is anywhere but the primary master, then you will need to trick windows using the "map" command. example:

This example assumes Windows to be on the secondary master (hd2). Grub starts counting at zero instead of one.