From owner-freebsd-hubs Thu Apr 3 19:39:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA12067 for hubs-outgoing; Thu, 3 Apr 1997 19:39:59 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA12062 for ; Thu, 3 Apr 1997 19:39:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id TAA08543; Thu, 3 Apr 1997 19:40:42 -0800 (PST) Message-Id: <199704040340.TAA08543@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: "Marc G. Fournier" cc: "Jordan K. Hubbard" , hubs@freebsd.org Subject: Re: Things moving around on ftp://ftp.freebsd.org/pub/FreeBSD In-reply-to: Your message of "Thu, 03 Apr 1997 23:30:51 -0400." From: David Greenman Reply-To: dg@root.com Date: Thu, 03 Apr 1997 19:40:42 -0800 Sender: owner-hubs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Thu, 3 Apr 1997, Jordan K. Hubbard wrote: > >> > The only thing that the mirrors would require would be a listing >> > of those subdirectories that are symlink'd so that appropriate mirror >> > 'branches' could be created... >> >> Well, they can get that for themselves anytime - it's not like >> the information's a secret or anything. ;-) > > No, I realize that...but the idea should be to make the transition >as painful as possible for everyone, no? It would be easier for you to >create a list and send it out once to the list then to have everyone >ftp'ng into the site to check out what the configuration looks like, no? :) > > It could also act as a quick confirmation that the "dreadful deed" >is done? :) The main problem with the notification thing is that we move archives around frequently on wcarchive (due to space shortages) and we have too many archives to even think about trying to notify people about this every time it occurs. There really needs to be a more automatic mechanism for dealing with this. I know that mirror can be told to follow all symlinks, but this is bad when you use symlinks within a filesystem (ports -> current/ports) because it will cause the mirror site to needlessly consume massive amounts of disk space. Mirror should be smarter about this. It should be able to tell when a symlink point outside of the current hierarchy and then follow the symlink when it sees that. Hmmm...maybe it already has support for that? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project