search for: 3bc86f99

...different lease parameters in response to the client's DHCP architecture ID). For this to be useful, my aim is that different pxe loader implementations to follow the arch-xxxx convention too; I'm proposing a similar change in petitboot: http://git.ozlabs.org/?p=petitboot;a=commitdiff;h=3bc86f99 I have a patch in development for u-boot too. In the petitboot & u-boot cases, the pxe loader code is already present on the machine, so we don't have the "which loader binary to serve" issue, only the "which config to use" one. > Now, with lpxelinux.0 you can also...

...in response to the >client's DHCP architecture ID). > >For this to be useful, my aim is that different pxe loader >implementations to follow the arch-xxxx convention too; I'm proposing a >similar change in petitboot: > > http://git.ozlabs.org/?p=petitboot;a=commitdiff;h=3bc86f99 > >I have a patch in development for u-boot too. > >In the petitboot & u-boot cases, the pxe loader code is already present >on the machine, so we don't have the "which loader binary to serve" >issue, only the "which config to use" one. > >> No...

In other words, the dhcp server has to start the client on the correct binary for it's arch and by virtue of running different bins, we can determine the most appropriate config file for the client? On Monday, February 24, 2014 9:13 AM, Gene Cumm <gene.cumm at gmail.com> wrote: On Mon, Feb 24, 2014 at 3:14 AM, Jeremy Kerr <jk at ozlabs.org> wrote: > When serving PXE config