grub/redhat9/suse9
 

hello iv been messing about with partitioning my hard drive any way the problem being this
when i started my computer suse started up and redhat did not show up in my boot loader so i put my first redhat cd in and booted from that i clicked on system rescue to go in to redhat any way now when i start my computer redhat starts up and iv got no suse showing in my boot loader what am i doing wrong i need them both to show up in my boot loader at the same time any help is very much appreciated thanks nige

grub is your boot loader - right? Can you post your grub config file?
It will reside in /boot/grub/grub.conf in red hat. In suse (at least 9.0) the file name is something like menu1st (on my other box currently)

Here is a sample grub config for dual /multi booting

# 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,1)
# kernel /vmlinuz-version ro root=/dev/hdb1
# initrd /initrd-version.img
#boot=/dev/hda
default=0
fallback=1
timeout=10
#splashimage=(hd1,5)/boot/grub/splash.xpm.gz
splashimage=(hd1,5)/boot/grub/penguins.xpm.gz
title Windows98
rootnoverify (hd0,0)
chainloader +1
title Slackware 10
root (hd0,7)
kernel /boot/vmlinuz ro root=/dev/hda8 hdc=ide-scsi
title Red Hat 7.3 (2.4.20-30.7 custom)
root (hd1,5)
kernel /boot/vmlinuz ro root=/dev/hdb6
title Red Hat 7.3 (2.4.20-30.7.legacy)
root (hd1,5)
kernel /boot/vmlinuz-2.4.20-30.7.legacy ro root=/dev/hdb6
title Red Hat 9 (lvm)
root (hd1,1)
kernel /vmlinuz ro root=/dev/lv9/SAVE2
initrd /initrd-2.4.20-8.img
#title vector
# root (hd0,14)
# kernel /boot/vmlinuz ro root=/dev/hda15
#vmlinuz-2.4.25-1

I would settle on keeping this config file in redhat rather than suse. just a simple reason. grub 0.91 in rh allows a splash screen while grub 0.93 in suse (when it was on this box) didn't. Ok its your call anyway settle on one or the other.

read `info grub` esp about installing- its mainly describing an installation done at boot time; you can run these commands however inside rh/suse with grub-install...
hd0,0 says grub.conf (menu1st..whatever) is on the first partition of the primary master drive. adjust according to your configuration.

ONe thing about grub vs. lilo is that once yu've established this "link" (I suppose) to your conf file you don;t need to reinstall or update subsequently with conf file changes. i.e. add a new partition/distro/kernel imgae: just enter it into your grub.conf (|menu1st), save file , reboot.

hth

John

this is everthing in my file
"# grub.conf genera# ted 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/hda6
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-8)
root (hd0,0)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdc=ide-scsi
initrd /initrd-2.4.20-8.img
thanks nige

ok folks i just know ur all dying to help so here goes when i turn my computer on i am given a choice now i can either boot from floppy which will boot my red hat or just leave it and it will boot suse so although i can now use both systems i would still be like to be able to boot both systems from my boot loader

friend, please provide some more detail !!

when you turn on the machine without floppy, what exactly do you see first. (after any hardware - m/b specific logos) is it like "grub loading stage 1" is it "lilo something" .... do you get a boot menu with only SuSE as an option?

I can only guess that the suse install put it's config file the the grub "path" and that's what its defaulting to.

Just for fun, you can post your partitioning scheme.

while you're running suse, can you go to the /boot/grub directory and look for it's config file (menu1st?) ok just run

grep kernel /boot/grub/* --

what file(s) are listed?

again, you can get what you need by setting up a config file according to the specs, and running the grub install.