From owner-freebsd-small Thu Jan 24 13:46:47 2002 Delivered-To: freebsd-small@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 439D037B400 for ; Thu, 24 Jan 2002 13:46:46 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g0OLlD408407; Thu, 24 Jan 2002 13:47:13 -0800 (PST) Date: Thu, 24 Jan 2002 13:47:12 -0800 (PST) From: Doug White To: Atle Veka Cc: small@FreeBSD.ORG Subject: Re: Automatic FreeBSD install via PicoBSD? In-Reply-To: <20020123131208.D55706-100000@gilliam.users.flyingcroc.net> Message-ID: <20020124134612.J5882-100000@resnet.uoregon.edu> X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 23 Jan 2002, Atle Veka wrote: > We currently have 350+ FreeBSD installations on our network and are > constantly adding new servers and reinstalling (upgrading) old > installations. I am looking at creating a PicoBSD floppy that would > essentially make an installation as easy as possible and require little > intervention as our NOC attendants often make mistakes and we end up with > non-standard systems. Take a look at the install floppy image. I used this to install several machines at one of my previous employers. I'm not sure the image actually works, but the ideas are there. It just uses the PXE NFS mount and untars a tarball of the machine to install, then does some fixups. The guts are in the doinstall file stuck in /etc. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message