search for: autodisovery

.../mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd /mybootdir/pxelinux.cfg/C000025B [...] /mybootdir/pxelinux.cfg/C /mybootdir/pxelinux.cfg/default When serving PXE config files to machines of different architectures (requiring separate boot images and config files), this means we cannot use the autodisovery mechanism without having prior knowledge of a MAC/IP/uuid-to-architecture mapping. This change introduces an additional step to the autodiscovery process, using a name based on the client machine architecture. I use IANA's mapping of processor architecture types to DHCP option codes[1] to defi...

On Mon, Feb 24, 2014 at 3:14 AM, Jeremy Kerr <jk at ozlabs.org> wrote: > When serving PXE config files to machines of different architectures > (requiring separate boot images and config files), this means we > cannot use the autodisovery mechanism without having prior knowledge of > a MAC/IP/uuid-to-architecture mapping. Actually, you can. COM32 modules are not usable across architectures. I'd suggest separating them to different directories. I don't think I've documented this alternate strategy yet but the overv...

...: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 files to machines of different architectures > (requiring separate boot images and config files), this means we > cannot use the autodisovery mechanism without having prior knowledge of > a MAC/IP/uuid-to-architecture mapping. Actually, you can.? COM32 modules are not usable across architectures. I'd suggest separating them to different directories.? I don't think I've documented this alternate strategy yet but the overvi...