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'm trying to triple boot with XP on hda and RH (Hdc,2) en Debian (hdc,3), but I can't get grub to boot Debian (I posted the grub-conf file below)
I copied the Debian kernel to the boot section and can't find a initrd...img file in Debian (should I make one, and how?)
Could the problem be that all kerel and intird paths are relativ to /boot as the file says?
Anne
# 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/hdc2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd1,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.18-14)
root (hd1,0)
kernel /vmlinuz-2.4.18-14 ro root=LABEL=/
initrd /initrd-2.4.18-14.img
title Debian
root (hd1,2)
kernel /vmlinuz-2.4.18-bf2.4 root=/dev/hdc3
title DOS
rootnoverify (hd0,0)
chainloader +1
Look at this line in the comments above the file:
"# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)"
Are the Debian boot images in the same boot partition as the RedHat ones? If not, maybe they should be.
I looked at this, but was afraid to copy the /boot directory to the boot partition b/c about three files have the same name.
I was hoping -quit naively I'll admit to that- that I could link to the debian boot directory.
You have to copy your Debian kernel (the vmlinuz-thing) to your RedHat /boot partition, then it should work. As far as I remember from my Debian days the bf-2.4 kernel doesn't use an initrd, if it does I think Debian has it in the rootpartition (or symlinked from there).
It almost worked like that
I had to create a symlink to the debian boot directory in the Redhat /boot partition and then it worked.
Seams that while loading the kernel it looks for a boot directory within the current directory and with the kernel copied directly to the boot partition it didn't find it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.