GRUB using /boot partition for multiple Linux/Windows boot?
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.
GRUB using /boot partition for multiple Linux/Windows boot?
Hi, I need a little help configuring GRUB for a second Linux distro (Slackware) on my system that already has WindowsME and Red Hat 8.0.
When I installed RH8, it recommended to create a /boot partition, so I did.
When I look in my grub.conf file I see
Code:
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg...
Does this mean that for subsequent Linux entries in the grub.conf file, (in particular the Slackware that I'm about to install) GRUB is going to look for the kernel and initrd files in the /boot partition, which up to now contains only Red Hat stuff?
I've read a lot of posts saying, go ahead and just drop your new kernels into the /boot partition and you're done. I've also seen a lot of posts saying don't mix your kernels.
So, what if I don't want to mix my Slackware files in with the Red Hat files that are currently in the /boot partition? How does GRUB find them in Slackware's own partition? Do I even have a choice?
One thing to be careful with when installing a new system is LABEL vaules in grub.conf and /etc/fstab. Some OS's setups overwrite them making the old OS unusable until you change them - to save time I do this before the install.
You manually set up your grub.conf and /etc/fstab? Wouldn't the new OS setup still overwrite them, regardless of whether you changed them ahead of time or not?
Or are they smart enough to read that the entries have already been added correctly and therefore don't need to touch those files?
I don't mean in the way they change the files - I mean the way that the new partitions are being formatted with LABELS that already exist. If you look in /etc/fstab the first column may contain labels like LABEL=/ you should change this to the device name eg /dev/hda2. It is OK if you want to share a home partition but you can't really have two root partitions with the same label.
I was working late when that one first hit me and it took a while to click. Maybe someone will correct me but I haven't seen a valid reason for using LABEL values. So until I here differently I'm going to access the devices directly
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.