From owner-freebsd-stable Sun Mar 21 16:59:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id 40D5214CD1 for ; Sun, 21 Mar 1999 16:59:35 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 10Ot3H-0006Yu-00; Sun, 21 Mar 1999 16:58:47 -0800 Date: Sun, 21 Mar 1999 16:58:44 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Andrew McNaughton Cc: "Michael C. Vergallen" , Eddie Irvine , Keith Woodman , freebsd-stable@FreeBSD.ORG Subject: Re: Confusion In-Reply-To: <199903211506.DAA21908@aniwa.sky> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Andrew McNaughton wrote: > > That is what cvs was invented for .. and that I why I switched all my > > machines to FreeBSD when 2.2.6. was released. However I don't just run > > cvs on all those machines I have a dedicated box that cvs's all the code > > and then builds all the code and runs a number off test scripts that test > > all the code used in the production boxes and then sends me a report if > > it fails if not I upgrade the production box by mounting it's hd and do a > > automtic install then I log in to the production box check if any changes > > are required in /etc and reboot the server. My maximum downtime is 5 > > minutes per upgrade unless some hardware goes bad but that is not the > > fault of FreeBSD. > > I wonder if this is generic enough that the script should be part of the > distribution. > > Should FreeBSD be distributing scripts for maintaining build systems, testing > those build systems, and upgrading production systems from them? Already done. "make buildworld" on your build system, and "make installworld" everywhere else. > Andrew McNaughton Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message