From owner-freebsd-questions@FreeBSD.ORG Mon Sep 24 19:09:31 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8485216A417 for ; Mon, 24 Sep 2007 19:09:31 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from mail.itu.dk (pluto.itu.dk [130.226.142.18]) by mx1.freebsd.org (Postfix) with ESMTP id 61F7913C468 for ; Mon, 24 Sep 2007 19:09:30 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from localhost (unknown [10.0.0.3]) by mail.itu.dk (Postfix) with ESMTP id E7F2832D272 for ; Mon, 24 Sep 2007 21:09:28 +0200 (CEST) X-Virus-Scanned: amavisd-new at itu.dk Received: from superman.itu.dk ([130.226.142.5]) by localhost (daredevil.itu.dk [130.226.142.26]) (amavisd-new, port 10024) with ESMTP id tWGCgR0Qjt-I for ; Mon, 24 Sep 2007 21:08:57 +0200 (CEST) Received: from wimac.littlebit.dk (unknown [85.233.238.191]) by superman.itu.dk (Postfix) with ESMTP id 2CD049E68B for ; Mon, 24 Sep 2007 21:08:47 +0200 (CEST) Message-ID: <46F80B36.6020707@cederstrand.dk> Date: Mon, 24 Sep 2007 21:08:38 +0200 From: Erik Cederstrand User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <46F23834.1050004@cederstrand.dk> <46F39CAF.5030306@cederstrand.dk> <20070921205940.V15829@tribble.ilrt.bris.ac.uk> <20070924174200.GA8539@sandvine.com> In-Reply-To: <20070924174200.GA8539@sandvine.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Repeated PXE jumpstart X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:09:31 -0000 Ed Maste wrote: > 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? Someone suggested this approach, but it gets complicated when I add more benchmarking clients to the mix later in the project. I know I can add host-specific setup to dhcpd.conf, and it's possible to do similar things with NFS (I'm installing over NFS) to put the main server in charge of controlling the clients, but it gets complicated if they aren't rebooting synchronously. I'd rather have the clients be in charge of when they reinstall (e.g. when the distribution-building machine has completed the next set of install files). I like Jan Grants idea, but it'll only work if FreeBSD crashes and reboots, not if it hangs, drops to debugger etc. Still, better than nothing! But until I have more time to play around, I'll let the clients commit their post-benchmarking suicide. Erik