From owner-freebsd-hubs@FreeBSD.ORG Thu Jun 12 15:10:29 2003 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4ED6637B401 for ; Thu, 12 Jun 2003 15:10:29 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id E319D43F75 for ; Thu, 12 Jun 2003 15:10:27 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5CMAKhS029265; Thu, 12 Jun 2003 15:10:20 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from athlon.pn.xcllnt.net (localhost [127.0.0.1]) by athlon.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5CMAKK4012993; Thu, 12 Jun 2003 15:10:20 -0700 (PDT) (envelope-from marcel@athlon.pn.xcllnt.net) Received: (from marcel@localhost) by athlon.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h5CMAJhp012992; Thu, 12 Jun 2003 15:10:19 -0700 (PDT) Date: Thu, 12 Jun 2003 15:10:19 -0700 From: Marcel Moolenaar To: Ken Smith Message-ID: <20030612221019.GA12301@athlon.pn.xcllnt.net> References: <20030612180244.GG21995@electra.cse.Buffalo.EDU> <20030612211821.GQ21995@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030612211821.GQ21995@electra.cse.Buffalo.EDU> User-Agent: Mutt/1.5.4i cc: freebsd-hubs@freebsd.org cc: jdp@polstra.com Subject: Re: The recent thread... handling new releases X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Distributions Hubs: mail sup ftp List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2003 22:10:29 -0000 On Thu, Jun 12, 2003 at 05:18:21PM -0400, Ken Smith wrote: > On Thu, Jun 12, 2003 at 02:59:55PM -0400, Garance A Drosihn wrote: > > > I have wondered if cvsup could be smart enough to download files > > under one name, and then afterwards (on a later run) know to just > > rename that file to the official name for a public release. > > This is an "I don't know but can look into it". Even if the answer is > "Yes" though, it might be more important to focus on what motivated > the question. Yes. Once you know what you want to achieve (and why) it's easier to come up with mechanisms that do it. > With some research > maybe a mechanism that accomplishes the goal can be found that would > work for more transfer mechanisms (not sure what right now, but playing > games with hard links type thing maybe). Maybe split the problem space into 2 parts: 1. The actual data and the mechanisms for distributing it. Typical characteristics here are bandwidth consumption, transport delays and disk space usage. 2. The meta-data that describes the data and controls access. Small pieces of information you can more easily distribute to all mirrors at once and can be used to set/change mods, rename/move files, locking/unlocking directories, checksums, download statistics and the likes. Just a brainwave. Use anyway you want... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net