Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just set up Fedora on an unused hard drive on this this system. It has RH9 on the other drive and it's working fine.
At the Fedora install I chose to install grub with the idea of making it a dual boot system. This would have been dandy but unfortunately I didn't know what to put in for the boot commands for the RH9 installation. And I still don't.
I thought maybe I could look at the grub.conf file but of course that file is the problem so boy was I amused to find out I couldn't get any help there.
Well, I couldn't help but think that my lilo.conf.anaconda file might have the info in it that needs to be entered into the grub.conf file. Perhaps if I post it here, someone can look at it and tell me what needs to be in the grub file?
# 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/hda2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=20
splashimage=(hd0,0)/grub/splash.xpm.gz
password --md5 $1$.rXbQVh3$VZLw0phA9T4yuSUrJQiB8/
title Fedora Core (2.4.22-1.2197.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2197.nptl ro root=LABEL=/1 hdb=ide-scsi rhgb
initrd /initrd-2.4.22-1.2197.nptl.img
title Fedora Core (2.4.22-1.2115.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/1 hdb=ide-scsi rhgb
initrd /initrd-2.4.22-1.2115.nptl.img
Hi wjn,
Basically, you don't tell us if you have a boot partition on RH9. In your "red" lines you say to grub that the kernel is on the root directory of partition /dev/hdc1, when you state "root = (hd1,0)". But you say that "initrd" is in "/boot" directory of the same disk. And you say to the kernel "root=/dev/hdc1".
So, if you have a separated "/boot" partition where kernel and initrd are, you have to specify
Code:
root = (hd1,x) # x is the number of the boot partition /dev/hdcn - 1
kernel /vmlinuz-2.4.20-8 hdb=ide-scsi root=/dev/hdc1 # the real root partition (/)
initrd /initrd-2.4.20.8.img
If you don't have a separated boot partition, you need to specify
Code:
root = (hd1,x) # x is the number of the root partition /dev/hdcn - 1
kernel /boot/vmlinuz-2.4.20-8 hdb=ide-scsi root=/dev/hdc1 # the real root partition (/)
initrd /boot/initrd-2.4.20.8.img
If this hints are not enough, please post the results of "fdisk -l" to give us some hint of where are the partitions?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.