On Sat, Jan 28, 2017 at 12:17:40AM +0100, Sven-Volker Nowarra wrote: > I am netbooting many systems, and last recently stepped on the issue, that I > had an amd64 and an i386 client in the same network. I wanted to boot them > into a "full" OpenBSD (not ramdisk kernel). That is not possible with the > default installation, cause pxeboot can not distinguish between these > Intel/AMD systems. DHCP server can distinguish by MAC address, but then when > pxeboot is loaded, the kernel is per default "bsd". This must clash either > with i386 or amd64 architecture, whatever was dropped into tftpboot direcotry. > So I went through some older mailing list entries, adapted them, and updated > my meanwhile extensive netboot document. I updated this into a PDF, covering > many, many details (now ~50 pages). Wanted to give something back to the > community. The PDF is currently located here: > http://nowarra.ch/Volker/netboot_OpenBSD/170127_netbooting_OpenBSD60.pdf >
Thanks, interesting document. Isn't better to use rewrite/file remapping instead of hacking pxeboot? If an i386 machine would request /etc/boot.conf via tftp you could rewrite it to (based on fact you know that that machine is i386 - during provisioning) /etc/i386/boot.conf. For the client I suppose it would still think it gets /etc/boot.conf. j.
