From owner-freebsd-hubs Mon May 7 14:58:57 2001 Delivered-To: freebsd-hubs@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 9BA0237B422 for ; Mon, 7 May 2001 14:58:46 -0700 (PDT) (envelope-from jason@dstc.edu.au) Received: from azure.dstc.edu.au (azure.dstc.edu.au [130.102.176.27]) by piglet.dstc.edu.au (8.11.3/8.11.3) with ESMTP id f47LwYO28790; Tue, 8 May 2001 07:58:34 +1000 (EST) Date: Tue, 8 May 2001 07:58:35 +1000 (EST) From: jason andrade To: Will Andrews Cc: hubs@FreeBSD.ORG Subject: Re: We seriously need a cleanup on ftp-master In-Reply-To: <20010507164104.I3246@casimir.physics.purdue.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 1.0 (http://www.roaringpenguin.com/mimedefang/) Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 7 May 2001, Will Andrews wrote: > > I have always kept one usable Alpha -current snapshot on the FTP site. > > current.freebsd.org isn't mirrored, thus anyone wanting to access it has > > to do to that one site. Why mirror ftp.freebsd.org at all then? > > BTW, my experiences for the past several years is that connectivity to > > current.freebsd.org is less than usable quite often. > > Well, I doubt that many people use the snaps at all. So I think having > separate sites for them is an OK idea. Perhaps we should keep a small > number of "known working" snaps on the ftp site, I guess. i also doubt many people use the snapshots. from observation, they either checkout stuff via cvsup and make world, or else they use the RCs when that is publicised. the freebsd model of RCs was quite different this time around, from most of the other distros in that it was a relatively short period between going from RC1 -> RC5 -> release.. this meant except for the `main' archive, most mirrors i was trying to rsync from weren't catching up and a lot of users i talked to either didn't download a RC, or preferred to avoid all of this and just use cvsup to update instead. if snapshots are being distributed then IMHO this needs to be according to a well publicizied system: o limit the snapshots to only one releases per arch o don't ever have 600M iso files in any snapshots (unless we can think of some sensible way to avoid redownloading 600M each time this changes) o don't create any package trees within snapshots o ideally, have /snapshots/i386/4.X-snapshot etc.. and symlink 4.X-DATE to it to help rsync users not have to have the whole thing deleted and then refetched because the name of the root directory has changed, even if all the filenames are still the same within it. cheers, -jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message