From owner-freebsd-stable Sat Apr 19 15:17:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA18598 for stable-outgoing; Sat, 19 Apr 1997 15:17:32 -0700 (PDT) Received: from cerberus.partsnow.com (gatekeeper.partsnow.com [207.155.26.98]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA18593 for ; Sat, 19 Apr 1997 15:17:28 -0700 (PDT) Received: (from don@localhost) by cerberus.partsnow.com (8.8.5/8.6.9) id PAA00640; Sat, 19 Apr 1997 15:17:29 -0700 (PDT) Date: Sat, 19 Apr 1997 15:17:29 -0700 (PDT) From: Don Wilde To: Don Lewis cc: "Jordan K. Hubbard" , stable@freebsd.org Subject: Re: stable gotta be stable! In-Reply-To: <199704192210.PAA02616@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > In my case, the CD's are pretty useless, and I really don't much care > if formal releases are done, since I've added a number of local changes > to what we're running here. What I've been doing is tracking the 2.1 > tree using CTM. I upgrade one machine with "make world". I then do > a "make release", to build a customized release distribution that I > install on an internal anonymous ftp server. I can then install or > upgrade all the other machines from this server at Ethernet speed. > > --- Truck > What's CTM? I'll try an IP dl for one system, then try your make release solution. Mine are all nearby, so it's not a real problem to reconfigure the IP's and bring them inside the firewall to do the ftp install. TNX for the suggestion.