On Mon, Jan 23, 2017 at 08:39:17PM +1000, Jonathan Matthew wrote:
> For network boot clients, dhcpd(8) can supply a filename for the initial
> boot file for the client, which is something like pxeboot (or pxelinux.0).
> EFI and BIOS clients need different boot files, though, so the server
> needs to know what mode the client is booting in, in order to supply the
> right filename. RFC 4578 defines DHCP client option 93 for this purpose.
>
> The ISC dhcpd approach to using this looks something like this:
>
> option arch code 93 = unsigned integer 16;
>
> if option arch = 00:00 {
> filename "bios/pxelinux.0";
> } elsif option arch = 00:07 {
> filename "efi.x64/syslinux.efi";
> }
>
> which seems a bit complicated, and also a lot of work to implement. Instead
> I propose adding 'efi-filename' (and 'efi32-filename', though I'm not sure
> that's worth doing) next to the existing 'filename' statement and having
> dhcpd itself interpret the option values to figure out which one should be
> used.
'filename' or 'option bootfile-name' are used by autoinstall. I'm not
sure diverting dhcpd option for boot image from rest of world is good
way. IIUC OpenBSD dhcpd doesn't support conditionals...
j.
