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
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;
Hi!
I'm trying to set up a system to continually and automatically run
benchmarks on the most recent CURRENT. The idea is to PXE-boot the
server, do an automated jumpstart installation, reboot and run a few
benchmarks. Lather, rinse, repeat.
My problem is when the jumpstart installation
Found the answer elsewhere, so this is just for the records...
Erik Cederstrand wrote:
Hi!
I'm trying to set up a system to continually and automatically run
benchmarks on the most recent CURRENT. The idea is to PXE-boot the
server, do an automated jumpstart installation, reboot and run a
On Fri, 21 Sep 2007, Erik Cederstrand wrote:
Found the answer elsewhere, so this is just for the records...
# sysctl kern.geom.debugflags=16
# dd if=/dev/zero of=/dev/ad0 bs=512 count=1
wipes the MBR and solves my problem.
The alternative is to put PXE ahead of the HD in the boot order,
