From: Matthew Garrett <mjg59@coreos.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH 4/4] Allow protocol to be separated from host with a semicolon
Date: Tue, 24 Jan 2017 20:25:22 -0800 [thread overview]
Message-ID: <CAPeXnHuMxXqHDs3W_HoFvsJVNBMYjGqp+UgGL7j5SRwSBnzx6w@mail.gmail.com> (raw)
In-Reply-To: <a0381e34-c561-e5a7-459e-68cc49f0435a@gmail.com>
On Tue, Jan 24, 2017 at 8:15 PM, Andrei Borzenkov <arvidjaar@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?
>> 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.
next prev parent reply other threads:[~2017-01-25 4:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 0:35 Misc network boot patches Matthew Garrett
2017-01-24 0:35 ` [PATCH 1/4] Allow non-default ports for HTTP requests Matthew Garrett
2017-01-29 6:50 ` Andrei Borzenkov
2017-01-24 0:35 ` [PATCH 2/4] Send a user class identifier in bootp requests and tag it as DHCP discover Matthew Garrett
2017-01-24 6:09 ` Michael Marineau
2017-01-24 0:36 ` [PATCH 3/4] Don't allocate a new address buffer if we receive multiple DNS responses Matthew Garrett
2017-01-24 3:55 ` Andrei Borzenkov
2017-01-24 20:52 ` Matthew Garrett
2017-01-24 0:36 ` [PATCH 4/4] Allow protocol to be separated from host with a semicolon Matthew Garrett
2017-01-24 4:02 ` Andrei Borzenkov
2017-01-24 20:50 ` Matthew Garrett
2017-01-25 3:48 ` Andrei Borzenkov
2017-01-25 4:06 ` Matthew Garrett
2017-01-25 4:15 ` Andrei Borzenkov
2017-01-25 4:25 ` Matthew Garrett [this message]
2017-01-25 6:56 ` Andrei Borzenkov
2017-01-25 7:16 ` Matthew Garrett
2017-01-25 7:37 ` Andrei Borzenkov
2017-01-25 9:00 ` Matthew Garrett
2017-01-25 6:18 ` Michael Chang
2017-01-25 6:21 ` Matthew Garrett
2017-01-25 8:35 ` Michael Chang
2017-01-25 9:02 ` Matthew Garrett
2017-01-25 17:30 ` Andrei Borzenkov
2017-01-25 23:33 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2017-01-23 23:45 [PATCH 1/4] Allow non-default ports for HTTP requests Matthew Garrett
2017-01-23 23:45 ` [PATCH 4/4] Allow protocol to be separated from host with a semicolon Matthew Garrett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPeXnHuMxXqHDs3W_HoFvsJVNBMYjGqp+UgGL7j5SRwSBnzx6w@mail.gmail.com \
--to=mjg59@coreos.com \
--cc=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.