On Mon, Jun 28, 2010 at 5:30 PM, Theo de Raadt <[email protected]> wrote: >> First the problem. Once a machine is automatically installed we want to >> change things so that it will boot from the hard drive. We have two >> possibilities. >> >> The first is to arrange so that the machine will boot first from the network >> and then from the hard drive. Once the install succeeds remove the >> dhcpd.conf entry and allow the pxeboot to timeout with no response. >> Works fine with only a small delay for the timeout. >> >> The second possibility is to allow the machine to pxeboot but tell it to boot >> from the hard drive with the newly installed system. If I do a standard install >> on wd0 and then tell pxeboot to use hd0a:/bsd the kernel will boot from >> wd0a but then it notices that it is pxebooting and tries to do an nfs_boot. >> Since I don't have diskless booting that fails and results in: >> >> panic: reverse arp not answered by rarpd(8) or dhcpd(8) >> >> boot(8) tells me to pass "-a" to have it prompt for the root device which >> works but that doesn't help if your not at the console (it also asks for the >> swap device). >> >> Before I start spelunking does anyone have any tips on how to set the >> root and swap device from boot.conf or any pointers to code where that >> capability might be added? Acceptable answers include that's stupid >> just let pxeboot timeout because you have to change something and >> it might as well be dhcp as /tftpboot/etc. > > There is no way to do what you want.
Maybe if the machine have ipmi(4), you can change the bootdev using ipmitool after the installation?
