On Thu, Jun 21, 2018 at 11:19 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: [snip] >> >>> OK anyway, I don't see broad BLS consensus forming yet, but I do see >>> two items that aren't controversial and could move forward as part of >>> this feature proposal: >>> >>> a. Consistent $BOOT/loader/entries for UEFI and BIOS where $BOOT is >>> the ESP on UEFI, and $BOOT is "other" on BIOS (most likely the >>> existing /boot ext4 volume currently used). i.e. do not put >>> /loader/entries in /EFI/fedora >> >> By "consistent", do you mean that both EFI and BIOS boot loaders will >> reference the same entry files? I like that. > > Yes. > >> However, I don't like the entries existing on ESP mostly because of the >> use case of md-RAID for /boot referenced in another thread. I think it >> would be best to just put the GRUB EFI file on ESP and put the rest of >> the bulk GRUB stuff in its utility partition (which may be RAID-ed). > > Right. The config + kernel + initramfs on traditional /boot can make > use of software raid, depending on static one time proper > configuration of each member drive's ESPs and now the ESPs never need > to be touched and thus not sync'd. > > Whereas constantly changing the ESP, means we need some way to > establish a master and rsync to the extras. > So the consensus seems to be to have the BLS fragments in $BOOT/loader/entries even on EFI, where $BOOT is the boot partition mounted on /boot. That will give us the following advantages as mentioned in this thread: 1. The BLS will not be stored in vfat, so ostree could keep using symlinks to do atomic swap of its /boot/loader/entries 2. The ESP won't be modified on kernels install / removal, that will make it easier for software RAID. 3. There will be consistency on where the BLS fragments are installed regardless of the firmware interface (EFI, BIOS, OPAL on ppc64le and zipl on s390x will all use /boot/loader/entries). I've updated the wiki page to reflect this and we will also change the implementation. Best regards, Javier _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/B3SMCSWFFEYIJIWPESY27MB6AMH3DH52/
