Re: [PATCH 4/4] Allow protocol to be separated from host with a semicolon

[Matthew Garrett]

On Tue, Jan 24, 2017 at 10:56 PM, Andrei Borzenkov <address@hidden> wrote:
> On Wed, Jan 25, 2017 at 7:25 AM, Matthew Garrett <address@hidden> wrote:
>> 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.

My experience is that configfile (http,example.com)grub/config works
as you'd expect it to, and that set
endpoint=$net_efinet0_dhcp_boot_file; configfile $endpoint does the
same. Am I hitting some corner case where things are being incorrectly
parsed and so giving me unintended functionality?

>> 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.

How are custom DHCP options handled? I can't find anything in the
documentation about them being interpreted, and a quick look at the
code only shows it setting known variables.