On 01/01/2017 06:10 PM, Chris Murphy wrote:
On Sun, Jan 1, 2017 at 1:45 PM, JD <jd1008@xxxxxxxxx> wrote:
Without having done it myself, I suspect that for the 2nd installation, grub
will
make write into /boot/grub2/grub.cfg file an entry that is similar to the
entry it makes
when it detects a windows bootable partition.
On BIOS firmware computers, yes. And it's the 2nd installation GRUB
that "owns" the drive. It is this grub.cfg whose generic entries
should be replaced using configfile to point to the 1st installations
grub.cfg. This is much more maintainable and compatible.
On UEFI firmware, there is only one fedora bootloader and grub.cfg, so
the 2nd installation will overwrite the 1st. I would modify the
installation so that each has its own grub.cfg found at /boot/grub2
just like it's a BIOS setup (and is supported by upstream GRUB as they
do it this way by default, I'm baffled why Fedora does this
differently). And then create a minimalist grub.cfg on the efi system
partition that points to the two installation specific grub.cfgs by
using configfile command.
I am not certain how many bootable partitions per disk grub2 supports.
A lot. It's limited by GRUB's ability to ennumerate, i.e. hdXmsdosY,
where the practical limit of Y is maybe something like 128. It
supports loading the kernel+initramfs on almost everything: md raid5
degraded; LVM, primary or extended MBR partitions, LUKs encrypted
volumes, Btrfs, ZFS, it's quite impressive what it can do. What
Thanx Chris.
As soon as I have another drive, I will try to put on it 2 fc25's and will
post the behavioral results and the diff results of the grub.cfg files.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
