From owner-freebsd-current Thu May 16 21:22:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA09157 for current-outgoing; Thu, 16 May 1996 21:22:18 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA09138; Thu, 16 May 1996 21:22:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id WAA06771; Thu, 16 May 1996 22:21:34 -0600 (MDT) Message-Id: <199605170421.WAA06771@rover.village.org> To: Nate Williams Subject: Re: Standard Shipping Containers - A Proposal for Distributing FreeBSD Cc: "Richard Wackerbarth" , "FreeBSD Hackers" , "FreeBSD Current" , "freebsd-stable@freebsd.org" In-reply-to: Your message of Thu, 16 May 1996 18:40:46 MDT Date: Thu, 16 May 1996 22:21:33 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > The Distribution: > There are seven distribution channels upon which I will comment. > 1) Direct access to the master tree. This really applies only > to the cvs tree and is "the only way to go" for commiters > who are well connected. > 2) Using "mirror". > 3) Using "mirror" with directory listing cached on the server. > 4) Using "sup". > 5) Using "ctm". > 6) Using distribution tarballs. > 7) Using the "live file system" from CD. > > Characteristics of the Distribution Mechanisms. > a) Only (1) and (2) provide "up to the minute" copies. Err, ummm, ctm provides me with up to the last four hour update copies of the development tree. And I have my email setup to automatically apply it, so it is no muss, no fuss. Easily more up to date that sup ever was for me. I resisted for a long time going to ctm because I thought it wouldn't give me the access that sup gave me. It has worked 1000% better than sup ever did for me. This is usually sufficient because relatively little changes in any given four hour period. Warner