On Thu, May 27, 2021 at 12:49 PM Luiz Angelo Daros de Luca <luizl...@gmail.com> wrote: > > My proposal would be an additional source for grubenv. SUSE still uses > the FS /boot/grub2/grubenv to store a > env_block variable (as well as other variables) that, if present, will > point to where an additional grubenv should be. My proposal is quite > the same, > but not limited to BTRFS. > > grub2-mkconfig could be opportunistic, using only /boot/grub2/grubenv > when it is writable by grub, /boot/EFI when present, btrfs first > blocks or stage1.5 data when everything > else fails. Grub and userland tools would only need to check if the > "normal" grubenv does define a "$grubenv_device", "$grubenv_block" or > "$grubenv_include".
I think it's better than the original proposal, and better than a file system mounted at /boot/grubenv only for that purpose. I'd like to see more consistency, fewer exceptions. And that also means the old argument about the MBR gap. GRUB should have its own partition here too. Chris Murphy _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
