From owner-freebsd-hubs@FreeBSD.ORG Wed Nov 17 07:20:26 2004 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 93E0616A4CE for ; Wed, 17 Nov 2004 07:20:26 +0000 (GMT) Received: from exhsto1.se.dataphone.com (exhsto1.se.dataphone.com [212.37.6.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F49B43D62 for ; Wed, 17 Nov 2004 07:20:25 +0000 (GMT) (envelope-from patrik.forsberg@dataphone.net) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 17 Nov 2004 08:20:19 +0100 Message-ID: <375DD163B075E34EA3C10A6286E34A5472E2E7@exhsto1.se.dataphone.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: freebsd 5.3-release and some observations Thread-Index: AcTMZm2l94Dm/QN/Tb24heCRISIGrQADOB4g From: "Patrik Forsberg" To: Subject: RE: freebsd 5.3-release and some observations 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, 17 Nov 2004 07:20:26 -0000 > i've finally finished updating the ISO trees and release trees > for the FreeBSD 5.3-RELEASE on ftp.au.freebsd.org and working > on ftp2.au.freebsd.org - it has taken a while given the > original release date. how are other admins going with this ? Well, we have enough speed to the closest ftp-master so we aculy had the full chrunk mirrored the same day it was out. > given the length of time for package tree updates i'd be > asking if there is any thoughts that could be raised about > how better to supply package trees so they aren't `tied' > to an architecture and thus appear to be released in 3-5G > chunks. Updates seem to go throw all the time from looking at the cvsup log.. Im not keeping any archived logs of the ftp-mirror so cant tell how that is performing. > i've also been asked if (as other distros are doing) FreeBSD > will master a DVD iso image for downloads. > > > i'm a little confused about the -current package trees in ports/$ARCH. >=20 > alpha has: >=20 > packages-5.2.1-release pointing at packages-5.2 and no > packages-5-current but it does have packages-4-stable >=20 > amd64 has: >=20 > packages-5-current AND packages-6-current >=20 > i386 has >=20 > packages-4-stable, packages-5-current AND packages-6-current >=20 > ia64 has >=20 > packages-5-current >=20 > sparc64 has >=20 > packages-5-current This can probably be explained by reading the .message file in the ports/i386 dir of the mirror " These are packages for the i386 architecture. Here are brief descriptions of each subdirectory. packages-4-stable: Packages for FreeBSD-4-stable. Updated weekly. packages-4.9-release: Packages for FreeBSD 4.9-release. packages-4.10-release: Packages for FreeBSD 4.10-release. packages-5.2.1-release: Packages for FreeBSD 5.2.1-release. packages-5.3-release: Packages for FreeBSD 5.3-release. *packages-5-current: Packages for FreeBSD-5-current. Updated weekly. *packages-6-current: Packages for FreeBSD-6-current. Updated weekly. (* - packages-5-current is currently unavailable .. sorry for the inconvenience) Unless noted otherwise, contents of these directories will not change except for critical bugfixes. " > is there a uniform standard that can be applied across the=20 > various architectures=20 > or is that not possible ? how often are the -current package=20 > sets being updated ?=20 > once upon a time it was a weekly (?) rebuild. should mirrors=20 > carry this ? if not,=20 > should -current package sets be moved out into a completely=20 > separate '-current'=20 > server layout ? just as there's a separate freebsd-archive=20 > layout/server area. The only thing I seem to be missing in the other architectures seem to be a .message file .. ? Regards, Patrik F ftp5/cvsup2/www2 .se.freebsd.org