On Wed, Jan 25, 2017 at 12:35 AM, Michael Chang <mch...@suse.com> wrote: > On Tue, Jan 24, 2017 at 10:21:22PM -0800, Matthew Garrett wrote: >> We're passing the bootfile to grub in order to obtain further >> configuration, so the firmware isn't relevant here. > > I mean that firmware may not be involved for now but it may be helpful someday > to carry that very same config booted by firmware as is.
The information is there. If local configuration doesn't choose to do something that overrides it, it will stay there. > And firmware did have implications to $prefix, if it's not been set, the value > would be the booted device and path pass by firmware. To keep from ABI > conflicts in modules loaded from elsewhere, you should not change it (in that > further configration) unless you know the modules will always be compatible in > new $prefix location. The DHCP server provided the initial copy of grub, so it should ensure that it only provides links to configuration that will provide compatible modules. This is no worse than supporting reading config fragments off disk that might redefine prefix. _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
