From owner-freebsd-current  Fri Feb 25  7:25:57 2000
Delivered-To: freebsd-current@freebsd.org
Received: from forrie.net (forrie.net [216.67.12.69])
	by hub.freebsd.org (Postfix) with ESMTP id C796537BDF5
	for <freebsd-current@freebsd.org>; Fri, 25 Feb 2000 07:25:54 -0800 (PST)
	(envelope-from forrie@forrie.com)
Received: from Forrest (getbent@forrie.ne.mediaone.net [24.147.129.124])
            by forrie.net with id e1PFPnj71718
            for <freebsd-current@freebsd.org>; Fri, 25 Feb 2000 10:25:50 -0500 (EST)
Message-Id: <4.2.2.20000225102306.00c59600@216.67.12.69>
X-Sender: forrie@216.67.12.69
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 25 Feb 2000 10:23:37 -0500
To: freebsd-current@freebsd.org
From: Forrest Aldrich <forrie@forrie.com>
Subject: Streamlining FreeBSD installations across many machines
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Perhaps this would be of interest in CURRENT issues:


We have several servers that we plan on deploying across the US.  Their 
purpose in life is network status and monitoring.   The hardware profiles 
are exactly the same...

Currently, we're using DD to mirror a disk image onto a new installation, 
and them nanually tweaking all the necessary configurations.   It's 
tedious, and is going to get hellish with the amount we plan on deploying.

I'm wondering if there might not be a way to streamline this install 
process, such that a boot floopy and script could be created to take a 
minimum amount of information, and then "do the right thing" as for the 
install.   Things like putting in the packet filters, the kernel, IP 
config, etc.

Surely someone has done this before...?

Any pointers would be greatly appreciated.


Thanks!



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message