LinuxQuestions.org - doubt in editing "grub.conf" in multi distro machine

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - doubt in editing "grub.conf" in multi distro machine (https://www.linuxquestions.org/questions/linux-newbie-8/doubt-in-editing-grub-conf-in-multi-distro-machine-350543/)

doubt in editing "grub.conf" in multi distro machine

hi there,
i had windows XP and redhat 9
just now i installed slackware 10.1 on my machine, but haven't installed the lilo.conf.
now i'm inside the red hat and have mounted the slackware on "/mnt/slack"
....
now the entries of grub.conf of redhat 9 are

Code:

cat grub.conf

# grub.conf generated by anaconda

#

# Note that you do not have to rerun grub after making changes to this file

# NOTICE:  You do not have a /boot partition.  This means that

#          all kernel and initrd paths are relative to /, eg.

#          root (hd0,8)

#          kernel /boot/vmlinuz-version ro root=/dev/hda9

#          initrd /boot/initrd-version.img

#boot=/dev/hda

default=1

timeout=10

splashimage=(hd0,8)/boot/grub/splash.xpm.gz

title Red Hat Linux 9 (2.4.20-8)

        root (hd0,8)

        kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/

        initrd /boot/initrd-2.4.20-8.img

title Windows XP

        rootnoverify (hd0,0)

        chainloader +1

now when i'm looking inside the /boot of slack i'm getting

Code:

config            diag1.img      System.map            vmlinuz

config-ide-2.4.29  README.initrd  System.map-ide-2.4.29  vmlinuz-ide-2.4.29

its for the first time i'm trying to have multi distros.......so from this onwards i'm not pretty sure of doing what.?
but what i doubt is that there is no initrd.....img file in the slackware !!!
....
plz. tell me which file from /boot of slack should i copy into "gurb.conf" of redhat.

regards

I'd like to know how you're going to get it to work since I've planned about installing another distro, or two more, to be precise. :)

But you don't have to worry about the initrd img file missing, apparently Slackware has everything it needs to boot built into the kernel. You could try adding the following to your Red Hat grub.conf, although I'm certainly not sure about this. It really depends if you have Slackware on a single partition or more, I'm assuming it's on one.

title Slackware 10.1
root (hd[insert the correct one here])
kernel /boot/vmlinuz ro root=/dev/hdaX

Of course, replace X with the correct number. Maybe someone else who knows better should check that out before you try it, although I doubt it's going to fry your hard drive. :)

it all worked man!!!

Quote:

It really depends if you have Slackware on a single partition or more, I'm assuming it's on one.

title Slackware 10.1
root (hd[insert the correct one here])
kernel /boot/vmlinuz ro root=/dev/hdaX

Of course, replace X with the correct numbe

i had slackware on a single partition only.

thanks buddy

Here are the new entries of "grub.conf" of redhat 9

Code:

title Red Hat Linux 9 (2.4.20-8)

        root (hd0,8)

        kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/

        initrd /boot/initrd-2.4.20-8.img

title Slackware 10.1

        root (hd0,6)

        kernel /boot/vmlinuz-ide-2.4.29 ro root=/dev/hda7

title Windows XP

        rootnoverify (hd0,0)

        chainloader +1

Can someone tell me what does "root=LABEL=/" signifies here.....???

Quote:

kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/

regards

Glad to hear it worked. :) I don't know about root=LABEL=/ though.

root=LABEL=/ is just the name for your root partition. If you look at /etc/fstab it will tell you that LABEL=/ is mounted on /

Tux,