Quote:
Originally Posted by mschwendt
Consulting the official documentation seldomly isn't helpful. Doesn't the manual cover your installation scenario?
With GRUB 2, I still use old school chainloading of bootloaders to start multiple distributions. Each installation updates its own bootloader.
Sounds weird and unusual.
|
Hadrons123's reply suggesting to consult official documentation was unhelpful and not, as misunderstood, consulting official documentation itself. His reply implied that I did not consult the wiki.
What is "weird and unusual"?
Quote:
Originally Posted by dsmithhfx
You've got a couple of options: when you install Fedora (or pretty much any other linux distro), install grub to the root of the same volume (rather than the entire disk), then chainload it from the pre-existing bootloader. That way you should never need to manually update either bootloader.
The other option (which is what I'm using for two Fedora installations on the same hdd), is to mount the one hosting the bootloader (in my case, GRUB 1) using the usual "mount" command in the terminal, and manually edit its grub.conf using gedit as root (with GRUB 2 you would want to edit something else). That way I don't need to reboot into it first. If you're not sure what you're doing though, this carries the risk of making your pc unbootable.
You're going to need to familiarize yourself with some of these basic procedures in order to successfully administer a multi-boot environment going forward. You might find it less stressful and safer to practice on something like virtualbox.
|
I have my Fedora Grub2 installed to its own / partition.
So, I have two options:
CHAINLOAD or
Manually EDIT grub.cfg (grub2).
Thanks for the Direction and your time... I will research more about them and get back.