Well it's not a good recommendation to do what is explicitly not recommended by GRUB devs. grub-install spits out a warning if you try to do this, by the way. It requires the user pass --force for it to work. And --force also isn't supported by anaconda for 4-5 Fedora releases now. It can't be used if /boot is on XFS or LVM or md RAID, all of which lack boot loader padding areas, so fewer configurations are supported. You're better off using extlinux if you want something that supports installation to a partition.
On Nov 26, 2013, at 7:39 PM, Ralf Corsepius <rc040203@freenet.de> wrote:
> On 11/26/2013 11:56 PM, poma wrote:
>> On 26.11.2013 23:18, Michael Schwendt wrote:
>>
>>> That's because your setup is wrong. If I were you, I would install a
>>> bootloader into the boot sector of each of your /boot partitions and
>>> chainload them from your MBR.
>>
>> Are you kidding?
>
> I guess, he isn't. It's what I recommend, too. It's the only way to make sure the different OSes/distros bootloaders do not interfere with each other.
The earlier suggestion to have the primary grub.cfg include an entry using configfile to point to each distribution's grub.cfg is the better way to handle this. Each distribution updates only their own grub.cfg. And as far as I'm aware, no distribution ever re-runs grub-install, so the existing bootloader is only going to be "interfered" with by users reinstalling the bootloader or installing a new OS.
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org