Date: Mon, 24 Sep 2007 13:42:00 -0400 From: Ed Maste <emaste@phaedrus.sandvine.ca> To: Jan Grant <jan.grant@bristol.ac.uk> Cc: freebsd-questions@freebsd.org, Erik Cederstrand <erik@cederstrand.dk> Subject: Re: Repeated PXE jumpstart Message-ID: <20070924174200.GA8539@sandvine.com> In-Reply-To: <20070921205940.V15829@tribble.ilrt.bris.ac.uk> References: <46F23834.1050004@cederstrand.dk> <46F39CAF.5030306@cederstrand.dk> <20070921205940.V15829@tribble.ilrt.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 21, 2007 at 09:02:04PM +0100, Jan Grant wrote: > The alternative is to put PXE ahead of the HD in the boot order, and > call back to the deployment host at the end of installation (prior to > reboot) to signal a DHCP reconfiguration. > > It adds a PXE timeout to each boot; the upside is that replacing a > wedging or otherwise broken install is just a matter of reconfiguring a > DHCP server. You could instead load pxegrub and have it boot from the disk instead of waiting for the PXE timeout. Or, if you're willing to accept a network-booted loader, how about just having it load and boot the kernel from the disk? -Ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070924174200.GA8539>