Date: Fri, 17 Mar 2000 11:48:29 -0800 (PST) From: Kris Kennaway <kris@hub.freebsd.org> To: Forrest Aldrich <forrie@forrie.com> Cc: freebsd-current@freebsd.org Subject: Re: Streamlining FreeBSD Installations Message-ID: <Pine.BSF.4.21.0003171145110.41802-100000@hub.freebsd.org> In-Reply-To: <4.3.1.2.20000317074445.00b60d90@216.67.12.69>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 17 Mar 2000, Forrest Aldrich wrote:
> I was also curious about what people do to keep a fleet of FreeBSD
> machines up-to-date with CVSup and buildworld. I can't imagine
> manually going to more than 100 machines and doing the same thing
> manually... how time consuming.
Have a master cvsup server which runs the cvsupd-bin port and either
cvsups manually from an outsider server, or schedules it automatically.
Run cron jobs on each of the clients to cvsup from your local server and
buildworld (if any changes are picked up).
If you don't want to buildworld without testing the process first on a
scratch box, then run the cvsup on your cvsupd server manually once you've
verified it.
> To summarize again, we are deploying status monitoring machines into POPs,
> across the US. Those machines are identical in terms of hardware, et
> al. We were hoping to find a means by which to streamline the installation
> process, such that we could create (say) custom boot floppies where you'd
> input minimum information (IP address, hostname, domain, etc.) and it would
> then go off and perform the installation (from fdisk, newfs... to editing
> packet filters appropriately, which make require a "template" of sorts).
picobsd might come in handy here.
Kris
----
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
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.0003171145110.41802-100000>