Displaying 3 results from an estimated 3 matches for "autodisoveri".
Did you mean:
autodisovery
2014 Feb 24
3
[RFC, PATCH] core/pxe: Add architecture-specific discovery request for PXE config file
Currently, the TFTP configuration file discovery process will request a
set of files based on the UUID, MAC address, lease IP address and
eventually fall back to "default":
/mybootdir/pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d
/mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd
/mybootdir/pxelinux.cfg/C000025B
[...]
/mybootdir/pxelinux.cfg/C
/mybootdir/pxelinux.cfg/default
2014 Feb 24
0
[RFC, PATCH] core/pxe: Add architecture-specific discovery request for PXE config file
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
2014 Feb 24
2
[RFC, PATCH] core/pxe: Add architecture-specific discovery request for PXE config file
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