Date: Sun, 3 Dec 2006 10:14:57 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Garrett Cooper <youshi10@u.washington.edu> Cc: freebsd-hackers@freebsd.org Subject: Re: Tools for FreeBSD development Message-ID: <20061203101352.K40536@fledge.watson.org> In-Reply-To: <45728A19.7050300@u.washington.edu> References: <eb7c8e2e0612021224x13598151ya58e471c9dfaa3b4@mail.gmail.com> <eb7c8e2e0612021528h47239e5cl3cf0c1e08e399329@mail.gmail.com> <20061202210741.02e0728a@kan.dnsalias.net> <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> <20061203064956.GB2405@kobe.laptop> <45728A19.7050300@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 Dec 2006, Garrett Cooper wrote: > Giorgos Keramidas wrote: >> On 2006-12-02 20:05, Kevin Sanders <newroswell@gmail.com> wrote: >>> On 12/2/06, Alexander Kabaev <kabaev@gmail.com> wrote: >>>> I personally think that having a dedicated box in disk-less >>>> configuration is the best option out there. [...] >>> Alexander, when you say disk-less configuration, are you referring to >>> booting from a network image/server? That's an interesting idea. I'm >>> fairly new to FreeBSD development also, and prefer the speed of a >>> dedicated box, but recently suffered my first corrupted beyond repair >>> system. >> >> Yes, a "diskless" boot is a network-based boot :-) > > Look into BOOTP for that: > <http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-diskless.html>. > You may want to just use vmware (best reliable solution, IMO but it costs > money), depending on what resources you have on hand and what you're trying > to accomplish. If using FreeBSD on i386/amd64 boxes, use PXE. There are quite a few "instant setup" web pages out there that tell you how to get it running. pxeboot makes life incredibly easy, as you can load kernels, modules, configurations, etc, over NFS. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061203101352.K40536>