X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C540DD1D54B; Thu, 15 Jan 2004 00:11:27 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 54776-10; Wed, 14 Jan 2004 20:10:58 -0400 (AST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id BD32BD1D8AF; Wed, 14 Jan 2004 20:10:55 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id 7863B3B11C; Wed, 14 Jan 2004 20:07:54 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 75C173B05B; Wed, 14 Jan 2004 20:07:54 -0400 (AST) Date: Wed, 14 Jan 2004 20:07:54 -0400 (AST) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: "Ricardo Ryoiti S. Junior" Cc: Peter Eisentraut , Robert Treat , Alvaro Herrera , "Marc G. Fournier" , pgsql-advocacy@postgresql.org Subject: Re: FTP Mirrors (was Re: Rewriting the website) In-Reply-To: Message-ID: <20040114200559.W45512@ganymede.hub.org> References: <40014281.4060908@cs.msu.su> <200401142018.44331.peter_e@gmx.net> <1074115306.29165.373.camel@camel> <200401142358.06919.peter_e@gmx.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/254 X-Sequence-Number: 3436 I have nothing against making that change on the mail server, should have thought of that long ago, but, then again, nobody else has either ... This is going to involve a massive update on all the mirrors, since effectively everything will be moving at once ... is this something everyone agrees should happen, before I do it? On Wed, 14 Jan 2004, Ricardo Ryoiti S. Junior wrote: > Hi, > > On Wed, 14 Jan 2004, Peter Eisentraut wrote: > > > I think the directory structure should mirror exactly > > ftp.postgresql.org, so I can go to ftp.xx.postgresql.org and find the > > same things in the same places. If someone wants to mirror with > > arbitrary directory structure, they can do that, but since you're going > > to have to go through the web page anyway they don't have to carry the > > postgresql.org domain at all. > > > Right now, virtually no mirrors follow that rule. Is it so hard to set > > up virtual hosts on ftp servers? > > Regardless of virtualhosts, I think that ftp.postgresql.org's own > FTP server should be structured like /pub/PostgreSQL/v7.4.1... That's how > our mirror is setup and I believe that's the cleanest way to have more > than one mirror in the same server. This is also a good practice, since > not all (including ours) ftp daemons support virtual hosts. > > If we had all directories directly after /pub, there would be more > than 30 subdirectories, all mixed up: NetBSD, PostgreSQL, etc. Thus, > setting our mirror just like PostgreSQL's, without virtualhost, would be > very confusing for our clients. > > I agree that every mirror should use the same directory structure, > but asking everyone to place everything directly after /pub or setting up > virtualhosts doesn't seem to be plausible, mainly because there're a lot > of mirrors out there. > > So I think that the easiest (and cleanest) way is to change > postgresql's ftp to /pub/postgresql, asking new and current mirrors to > adopt that approach. It's much easier than asking for virtualhosts. Not > just because I wouldn't have to change my setup :) but also because many > projects with mirrors do that successfully. > Or, at least a /pub/postgresql link to the actual mirror directory > could be used... > > []s > Ricardo. > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664