Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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.
Preparing to install several distros on my external USB drive. Curious about GRUB2.
Should I install each OS in reverse order of likely use in order for successive GRUB2's to capture the existence of prior installs? Or is that even how it works?
I recommend that you make sure that the installer does *not* install a bootloader and then reboot into the original distribution afterwards and run:
Code:
# update-grub
To generate a menu entry for the new distribution.
The key is that the last distribution to install GRUB "controls" the bootloader -- ie, the configuration file in that distribution is the file that is parsed by the bootloader.
update-grub is a Debian-ism - not available in all distros.
Having once had the installer (Anaconda as it happens) refuse to install a kernel if you chose to not install the boot-loader, I am a little gun-shy of this now. I allow all systems to install a loader, but install the "favourite" system last - and boot into it to run mkconfig when the need arises.
As is usual in this namespace, more than one way to do it.
Just a few days ago, I installed Ubuntu 14.04 on a system that had Centos 7.1. The Centos boot menus where totally messed up as a result - what was labeled "rescue" was the normal kernel and vice versa, and they ended up with the wrong root device.
I would create the final grub config file manually, or keep copies of the intermediate grub config files as you progress with you installs. As a minimum, check everything when you are done.
Changing the order of the menuentry clauses shouldn't be a big deal.
Install 1st distro with separate boot partition mounted at /boot and grub2 in MBR
Unmount /boot, remount in /mnt/Boot
Copy everything in /mnt/Boot to /boot
Install grub in 1st OS's boot sector
Manually modify grub.cfg in boot partition to chainload 1st OS's bootloader
While additional OSs remain to be installed:
Install next distro in new partition (with grub in this partitions boot sector)
Manually modify grub.cfg in boot partition to chainload this OS's bootloader
Last edited by RockDoctor; 07-17-2015 at 07:26 AM.
Reason: formatting
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.