From owner-freebsd-arch@FreeBSD.ORG Sun Aug 7 16:08:03 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 D361916A41F; Sun, 7 Aug 2005 16:08:03 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24F6643D45; Sun, 7 Aug 2005 16:08:03 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j77G5Ijo081439; Sun, 7 Aug 2005 10:05:18 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 07 Aug 2005 10:06:22 -0600 (MDT) Message-Id: <20050807.100622.54623722.imp@bsdimp.com> To: cperciva@freebsd.org From: "M. Warner Losh" In-Reply-To: <42F61960.4020400@freebsd.org> References: <42F60443.2040301@freebsd.org> <20050807.231125.26489231.hrs@allbsd.org> <42F61960.4020400@freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 07 Aug 2005 10:05:18 -0600 (MDT) Cc: hrs@freebsd.org, freebsd-arch@freebsd.org Subject: Re: /usr/portsnap vs. /var/db/portsnap 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:08:04 -0000 In message: <42F61960.4020400@freebsd.org> Colin Percival writes: : Hiroki Sato wrote: : > Colin Percival wrote: : > cp> Hiroki Sato wrote: : > cp> > So, I would like the server-side bits to be imported if portsnap will : > cp> > be in the base system. : > cp> : > cp> By "server-side", do you mean : > cp> a) The code which builds the portsnap files, : > cp> b) The code which mirrors them, or : > cp> c) The web server (Apache) which actually sits on port 80 and : > cp> communicates with the portsnap client? : > : > a) and b). : : Those don't belong in src, but I could put them into the projects repo : if people really want them. I was planning on just providing them to : portmgr and secteam since there's no reason for anyone to be running : their own portsnap builds, Acutally, there are plenty of reasons. I've worked at places that did similar things to portsnap to create standard packages that were installed on all the machines of a certain type (workstation, server, etc). I can easily see large organizations wanting to do this. : very little reason for anyone to be running : a portsnap mirror unless it's a public mirror, Our experience with cvsup would suggest otherwise. Many places with large numbers or even small numbers of machines run cvsup mirrors that are private. I expect that universities will want to run mirrors that they might not want non-students accessing (eg, internal bandwidth is free, external is expensive). : and my experience with : FreeBSD Update is that making code available will result in people : trying to use it even if they really shouldn't be using it. That's the chance you take with open source. :-) : (I've had : many email exchanges about FreeBSD Update which basically ran "I can't : get the FreeBSD Update server code to work, help!", "Why do you want : to run the FreeBSD Update server code?", "Uhh... I have no idea. I'll : just download the client and use the updates you're building.") The world is full of idoits. It is also full of smart people who do smart things with technology. Don't let the idoits ruin it for the rest of us. Warner