Date: Tue, 21 Mar 2000 15:55:36 -0800 (PST) From: Doug White <dwhite@resnet.uoregon.edu> To: Pete <pmckenna@uswest.net> Cc: Brian Dean <brdean@unx.sas.com>, "Daniel C. Sobral" <dcs@newsguy.com>, Forrest Aldrich <forrie@forrie.com>, freebsd-current@FreeBSD.ORG Subject: Re: Streamlining FreeBSD Installations Message-ID: <Pine.BSF.4.21.0003211551180.50553-100000@resnet.uoregon.edu> In-Reply-To: <38D5B4C1.A170936A@uswest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 19 Mar 2000, Pete wrote: > It does not have to be that hands on. ... > I hacked PicoBSD to do this so it works from one floppy. You can > either name the file install.cfg in which case it is run automatically > or give it a ../stand/my_script.cfg to grab the build file you wish > from stand which is where I put my scripts on the build floppy. I have > about a dozen different scripts on the floppy and still seem to have > lots of room. I haven't automated adding users. I did this under 3.2 > and am trying to find the time to move it to 3.4 although it should be > able to build 3.4 servers with no problem. I took this one step further -- The PicoBSD Install floppy just pulls down a tarball of a running system, splats it on, and does anything else you want to/can do from a shell script. Works quite well and is easy to update -- install, change the image, rebuild image. You can even edit the install script on the floppy without rebuilding the floppy. We also don't bother to stay -STABLE -- we're on 3.2-S with some kernel hacks and it works fine, so we don't touch it :) 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-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0003211551180.50553-100000>