From owner-freebsd-hubs@FreeBSD.ORG Tue Jun 10 19:44:05 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 9346B37B401 for ; Tue, 10 Jun 2003 19:44:05 -0700 (PDT) Received: from luna.rtfmconsult.com (luna.rtfmconsult.com [202.83.72.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id C82AC43F75 for ; Tue, 10 Jun 2003 19:44:04 -0700 (PDT) (envelope-from jason@rtfmconsult.com) Received: by luna.rtfmconsult.com (Postfix, from userid 42) id 9E6CE48E6F; Wed, 11 Jun 2003 12:44:02 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by luna.rtfmconsult.com (Postfix) with ESMTP id 9608B52D95; Wed, 11 Jun 2003 12:44:02 +1000 (EST) Date: Wed, 11 Jun 2003 12:44:02 +1000 (EST) From: jason andrade To: Makoto Matsushita In-Reply-To: <20030611112908X.matusita@jp.FreeBSD.org> Message-ID: References: <7mwuftfjcs.wl@black.imgsrc.co.jp> <20030611112059M.matusita@jp.FreeBSD.org> <20030611112908X.matusita@jp.FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hubs@freebsd.org Subject: Re: Remove old 5.1-* bits 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: Wed, 11 Jun 2003 02:44:05 -0000 On Wed, 11 Jun 2003, Makoto Matsushita wrote: > matusita> And, how about 4.6.2-RELEASE for i386/alpha? We have removed all > matusita> packages for 4.6.2 already. > > Oops, s/alpha//; (i.e. packages-4.6.2-release is there for alpha). > Speaking about alpha, there's still 4.4-RELEASE which packages were no > longer there. > > Yet another "removing them all" candidate will be in > releases/${arch}/ISO-IMAGES directory. personally we (ftp.au) have archived all the older releases off the main freebsd area and at this stage are only keeping ISO images and RELEASE trees for 4.8-RELEASE, 5.0-RELEASE and 5.1-RELEASE for i386/alpha/amd64/sparc64 where relevant. the same for the package trees (ports) this means the data set requirements can broadly be classified as (in order of most demand from mirrors) FreeBSD releases (per architecture): RELEASE tree and ISO images FreeBSD packages (per architecture): package tree per release FreeBSD 'current' packages per architecture: 4-current and 5-current FreeBSD 'stable' packages per architecture: 4-stable and 5-stable FreeBSD distfiles and local distfiles FreeBSD CVSup tree [1] FreeBSD misc in the past i have been discussing with murray the possibility of setting up a 'FreeBSD-archive' server. i'm hoping to make such a machine available (assuming it doesn't exist already) sometime next month where all the older releases can be stored for posterity, hopefully back to 1.0 and beyond. i might require some assistance from people to dig up their old FreeBSD CD sets so we can re-create ISO images to be stored. it will probably be able to be mirrored from, so if there are sites out there that would like to keep some of the older releases around, is it ok to standardize on a directory name of /pub/FreeBSD-archive rather than trying to keep it 'within' the /pub/FreeBSD tree. regards, -jason [1] the cvsup source tree is in high demand but over a more constant time rather than the 'bursts' of a new release. cvsup users tend to be updating their servers more often to the latest -STABLE rather than doing 'fresh' installs when a new -RELEASE is out.