On Sun, Jan 29, 2017 at 01:17:48AM +0200, li...@wrant.com wrote: > Sample excerpts from host specific DHCP server config, for i386 and amd64: > > next-server 10.0.0.32; > filename "auto_upgrade"; > > next-server 10.0.0.64; > filename "auto_upgrade"; > > Quoting autoinstall(8) for netbooting: http://man.openbsd.org/autoinstall > > On architectures where the filename statement is used to provide the > name of the file to netboot it is necessary to create symbolic links > called auto_install and auto_upgrade that point to the expected boot > program and to change the value of the filename statement in the > dhcpd.conf(5) file to be auto_install or auto_upgrade. > > # ln -s /tftpboot/i386/pxeboot /tftpboot/i386/auto_upgrade > # ln -s /tftpboot/amd64/pxeboot /tftpboot/amd64/auto_upgrade > > Needless to say, you need to populate the /tftpboot/{i386,amd64} locations > with the system installation packages from the local mirror / compilation. > > It is also quite easy to combine both the DHCP server and two instances of > tftpd(8), started independently listening on 2 IP address aliases, serving > pxeboot(8) respectively for i386 and amd64 systems stand alone each other. > > See rcctl(8) to run a second copy of a daemon http://man.openbsd.org/rcctl > > The recommended way to run a second copy of a given daemon for a > different purpose is to create a symbolic link to its rc.d(8) control > script: > > # ln -s /etc/rc.d/tftpd /etc/rc.d/tftpd2 > # rcctl set tftpd status on > # rcctl set tftpd2 status on > # rcctl set tftpd flags -4 -l 10.0.0.32 /tftpboot/i386 > # rcctl set tftpd2 flags -4 -l 10.0.0.64 /tftpboot/amd64 > # rcctl start tftpd > # rcctl start tftpd2
Nice trick to define multiple tftp servers for each x86 architecture :) Thanks! j.
