From owner-freebsd-stable Sat Oct 24 11:20:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28759 for freebsd-stable-outgoing; Sat, 24 Oct 1998 11:20:55 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28754 for ; Sat, 24 Oct 1998 11:20:54 -0700 (PDT) (envelope-from rkw@Dataplex.NET) From: rkw@Dataplex.NET Received: from dataplex.net (nomad.dataplex.net [208.2.87.8]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id PAA14768; Sat, 24 Oct 1998 15:01:50 -0500 (CDT) (envelope-from rkw@dataplex.net) Message-Id: <199810242001.PAA14768@shrimp.dataplex.net> Date: Sat, 24 Oct 1998 13:19:03 -0500 (CDT) Subject: Re: Stable and CTM To: dean@odyssey.apana.org.au cc: freebsd-stable@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25 Oct, Dean Hollister wrote: > Why not just use cvsup? 1. cvsup provides a custom update for each individual user. ctm is broadcast publication. For a large number of users, cvsup requires more server-side resources. 2. cvsup requires a direct realtime connection from the client to a cvsup server, ctm uses "store and forward" technology which can even run on "sneaker net". The intermediate servers are generic internet servers rather than something particular to the particular project. 3. cvsup requires that each machine connect to the cvsup server while it parses its tree. Even if there is little changed, this can take quite some time. Some connections are very expensive per minute. Some connections cannot be maintained for sufficient time to do the update. 4. Ctm provides an "audit trail". In the past, this has proven valuable when it became necessary to reconstruct the master cvs tree. Don't misunderstand. Cvsup is a fine way to update certain classes of users. In fact, the ctm generator uses cvsup to retrieve its input. However, not everyone fits into the same mould. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message