From owner-freebsd-stable Wed Mar 26 13:36:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA28805 for stable-outgoing; Wed, 26 Mar 1997 13:36:26 -0800 (PST) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA28799 for ; Wed, 26 Mar 1997 13:36:23 -0800 (PST) Received: from [204.69.236.50] (GATEWAY.SKIPSTONE.COM [198.214.10.129]) by shrimp.dataplex.net (8.8.5/8.8.5) with SMTP id PAA01731; Wed, 26 Mar 1997 15:36:10 -0600 (CST) Date: 26 Mar 97 15:38:18 -0600 Subject: Re: SUP From: "Richard Wackerbarth" To: "Warner Losh" Cc: stable@freebsd.org X-Mailer: Cyberdog/2.0b1 MIME-Version: 1.0 Message-Id: Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, Mar 26, 1997 1:55 PM, Warner Losh wrote: >That's true. I just wanna know what the most supported way is at the >moment. I don't have a problem switching to something else as long as >it has approx the same charactersitics as sup: relatively low latency, >gets the whole tree, etc, etc. I'm thinking of actually moving it >over to CTM I feel certain that both CVSup and CTM will be around for some time. They each have characteristics which make them superior to the other for certain "customers". I would STRONGLY encourage EVERYONE to use CTM rather than CVSup if they are routinely updating (be it daily or weekly). CTM has the advantage of being both "push" technology and "store and forward". Its drawbacks are that it does not do dynamic recovery of partially trashed trees and that it updates only periodically. However, there are very few individuals who do not have direct access to freefall and really need updates more than once or twice a day. As for rebuilding partially trashed trees, I would argue that it that is necessary other than on extremely rare occasions, the user is not practicing "safe hex" and should change their methodology.