On Tue, Jan 24, 2017 at 10:21:22PM -0800, Matthew Garrett wrote: > On Tue, Jan 24, 2017 at 10:18 PM, Michael Chang <mch...@suse.com> wrote: > > On Tue, Jan 24, 2017 at 12:50:37PM -0800, Matthew Garrett wrote: > >> The DHCP server will return a string in the boot_file field. If you > >> want to indicate that this file should be obtained over http, the > >> easiest way to handle this is to provide a boot file in the form > >> (http,host)filename. Unfortunately dnsmasq uses commas to tokenise its > >> configuration parameters and there appears to be no way to override > >> that, which makes it impossible to provide a boot file in this form. > >> Allowing the use of an alternative character avoids this problem. > > > > To my understanding, you can (and have to) use the url form in boot-file and > > specify vendor-class-identifier to "HTTPClient" to let the UEFI firmware > > knows > > this as a response to HTTP boot request and handle that boot-file > > accordingly, > > then continue with that url loaded and run as NBP. > > 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. 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. Thanks, Michael > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
