From owner-freebsd-arch@FreeBSD.ORG Sun Aug 7 16:48:58 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40D1E16A41F; Sun, 7 Aug 2005 16:48:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD1D644133; Sun, 7 Aug 2005 16:48:57 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j77H0nZC007176; Sun, 7 Aug 2005 11:00:49 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42F63B6D.3080909@samsco.org> Date: Sun, 07 Aug 2005 10:48:45 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <42F62C5F.6000609@freebsd.org> <20050807.101746.68985623.imp@bsdimp.com> In-Reply-To: <20050807.101746.68985623.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: cperciva@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Adding portsnap to the base system X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2005 16:48:58 -0000 M. Warner Losh wrote: > In message: <42F62C5F.6000609@freebsd.org> > Colin Percival writes: > : I've been told by a committer that there hasn't been enough > : discussion about the merits of adding portsnap to the base > : system. > : > : The basic summary, for anyone who didn't read yesterday's > : thread, is that portsnap is a secure, easy to use, fast, > : low-bandwidth, and lightweight way to keep the ports tree > : up to date. It is currently used by about 2000 systems each > : week (based on my server logs; and increasing at a rate of > : about 50% per month). The feedback I've had from users has > : been universally glowing, aside from the complaints that it > : really should be in the base system already. > : > : Portsnap is not a complete replacement for CVSup -- it only > : handles ports, and it only handles the tree, not the repo -- > : but it is very good at doing the job it is designed for. > : > : Discuss. > > I'm confused. Earlier in this thread it looked like someone said it > distributed binaries. Now this seems to indicate it is just cvsup in > checkout mode. Which is it? And when posting questions like this, it > is usually good to include pointers to documentation (although the > diff below does contain the man pages). > > : Unless I hear any complaints, I'm going to commit the following > : patch tomorrow: > : http://www.daemonology.net/tmp/portsnap-base.diff > > Is there some reason you've reinvated fetch as well? What does > phttpget do that fetch(1) or fetch(3) doesn't? The only thing that > looks like it might is pipelining mode, which would be better in the > base fetch program, imho. > > neither make_index nor phttpget have man pages. > > What does this buy you over cvsup/cvsupd? > > Warner I'll save Colin from repeating the answer to this for the millionth time. 1. security 2. much lower bandwidth 3. why are you quibbling over a feature that is 40k, has already been well tested, and has the support and desires of users? If you're really concerned about confusion and duplication, I see plenty of much more worthy opportunities in the pccard/cardbus, natm/patm/hatm, etc spaces. Scott