From owner-freebsd-questions Fri Mar 10 7:48:33 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp.whitebarn.com (Spin.WhiteBarn.Com [216.0.13.113]) by hub.freebsd.org (Postfix) with ESMTP id 832BF37B97C for ; Fri, 10 Mar 2000 07:48:28 -0800 (PST) (envelope-from Bob@WhiteBarn.Com) Received: from WhiteBarn.Com (BarnStorm.WhiteBarn.Com [216.0.13.81]) by smtp.whitebarn.com (8.9.3/8.9.3) with ESMTP id JAA35700 for ; Fri, 10 Mar 2000 09:48:22 -0600 (CST) (envelope-from Bob@WhiteBarn.Com) Message-ID: <38C91945.1ECADEC4@WhiteBarn.Com> Date: Fri, 10 Mar 2000 09:48:22 -0600 From: Bob Van Valzah Organization: WhiteBarn Web Works X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Subject: Tools for Capturing/Cloning System Configuration? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a tool to capture the configuration of a running machine so that it can be easily cloned or rebuilt from a new release? Is anybody working on one? Here's why I ask: I have machines that're cvsup'd with the -CURRENT and -STABLE trees but these aren't "production" machines. If these trees are broken and I end up building a system that panics it's no big deal. But the majority of machines I run are in "production" and have complex configurations. They're running older -RELEASE bits. I can't afford to take these out of service while I load a new release of FreeBSD, load all the required packages and ports, recover the contents of all the config files, rebuild all the symlinks in root, reload all required CPAN modules, and generally cauterize the wounds opened by such a "brain transplant." Yes, I know I could use the "update" option of sysinstall, but the chances of that working well go down as the spread between the old and new releases goes up. It also leaves me with that terrible future uncertainty every time something doesn't work--is it broken because there's still a piece of the old release laying around? I run my production machines from -RELEASE code and packages precisely because I want the assurance that all the pieces will work together. So I'm trying to find tools that'll survey the configuration of a running machine and take note of how its configuration differs from a freshly installed system. The output from such tools could be an install.cfg file that's fed into sysinstall, a Makefile and set of diffs that're fed into patch, instructions for CPAN::Shell, etc. I'm a little way down the road to a Perl script that'll do the surveying and building of the above files. But I thought I'd better ask if there wasn't already something like this out there. All comments appreciated. Thanks, Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message