On Mon, Jan 23, 2017 at 09:57:28PM +1100, Jonathan Gray wrote:
> 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
> > 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";
> > }
>
> [...] IIUC
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
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
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
