From owner-freebsd-current Fri Feb 25 9:37:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 20D3237B920 for ; Fri, 25 Feb 2000 09:37:21 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA70913; Fri, 25 Feb 2000 09:37:02 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002251737.JAA70913@gndrsh.dnsmgr.net> Subject: Re: Streamlining FreeBSD installations across many machines In-Reply-To: <4.2.2.20000225102306.00c59600@216.67.12.69> from Forrest Aldrich at "Feb 25, 2000 10:23:37 am" To: forrie@forrie.com (Forrest Aldrich) Date: Fri, 25 Feb 2000 09:37:02 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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. A much faster way to do this is to just dd the first few megabytes of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use dump | restore to populate the disk. (We actually have 3.x and 4.x recent build filesystems that are built weekly on a master loading machine just for this purpose.) We mass produce system disk this way and it is much faster than a whole disk image operation especially when dealing with drives much larger than 2G bytes. > 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...? We do it on a weekly basis, 4 to 32 disks at a time... > Any pointers would be greatly appreciated. Hope this gives you some ideas... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message