On Wed, Jan 25, 2017 at 7:25 AM, Matthew Garrett <mj...@coreos.com> wrote: > On Tue, Jan 24, 2017 at 8:15 PM, Andrei Borzenkov <arvidj...@gmail.com> wrote: >> 25.01.2017 07:06, Matthew Garrett пишет: >>> I don't understand - grub_net_open_real() already handles this case: >> >> Because bootfile from DHCP packet is not used to set device part of >> $prefix. Setting bootfile to (http,host)filename will end up with full >> prefix "(tftp,$next_ip)(http,host)base-name-of-filename". If you mean >> something different, please explain. > > If prefix isn't set then won't bootfile be interpreted as the device plus > file? >
No. That would mean "parsing URI" that I mentioned. >>> Because we ship prebuilt images but don't know what IP addresses users >>> will be using for their deployment servers. >>> >> >> I can think about implementing URI parsing (somewhat in line with UEFI >> HTTPboot spec) and/or supporting partial $prefix that sets only >> protocol, something like "grub-mknetdir --prefix=(http,)", where server >> part is filled from DHCP ACK. > > We need the ability to pass port as well, so that would still be insufficient. Good. So start with design proposal that is extensible enough. But TBH - all of this can already be implemented using grub scripting. Use custom DHCP options or parse bootfile using regex. No code changes is needed - we support generic scripting for a reason. _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel