(These opinions are based on Oracle Solaris):
Some grub entries may not specify a bootfs, in which case, GRUB should
derive it from the bootfs property in the pool

bootfs is an annoying one since on-disk AFAIK only its objnum is stored
so we need to scan to determine its name. But for me it's only
backward-compatibility issue. This property shouldn't be necessary with
new or autodetected config.

The key issue is that it's possible to have BEs on a system that predate the installation of GRUB2, so if one of THOSE BEs change the default bootfs (which they will, since the beadm activate subcommand does just that), the grub.cfg would be out of date. I don't see any alternative to having GRUB2 do the scan to map the bootfs object to a zfs name :(.

 --S

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Reply via email to