Date: Fri, 18 Jul 2003 21:43:11 +0200 From: "Simon L. Nielsen" <simon@nitro.dk> To: Ken Smith <kensmith@cse.Buffalo.EDU> Cc: freebsd-hubs@freebsd.org Subject: Re: Mirror Requirements - Last question? Message-ID: <20030718194311.GF415@nitro.dk> In-Reply-To: <20030718181825.GD9029@electra.cse.Buffalo.EDU> References: <20030718174703.GC9029@electra.cse.Buffalo.EDU> <3F17FBEB.19412.3E93010D@localhost> <20030718181825.GD9029@electra.cse.Buffalo.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
--N1GIdlSm9i+YlY4t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2003.07.18 14:18:25 -0400, Ken Smith wrote: > On Fri, Jul 18, 2003 at 01:53:47PM -0400, Dan Langille wrote: >=20 > > Where do the "other" mirrors fit in? Some mirrors don't even cover=20 > > the full production release. Just bin/floppies/tools etc. >=20 > Just my opinion, open to suggestions... How about making some kind of list of what each mirror carry? Not on file level, but the major parts. E.g. a mirror can carry : stable i386 ISO images, stable release i386 packages, current/new tech amd64 packages and so on. It could be partially automated by a scripts that checks the content on the mirrors. E.g. redhat uses something like this: http://www.redhat.com/download/mirror.html . The sysinstall mirrors list could the generated from this mirror list. Just an idea, which might be overkill, but since it seems very hard to define what non-full mirrors should carry this might be a way to solve handle it. --=20 Simon L. Nielsen --N1GIdlSm9i+YlY4t Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/GE3P8kocFXgPTRwRAmOrAJ9W6r8jYSO4HGVLAjXTnxmTRR2lowCgrmxF rpbVbXnjcwUHFd3kuLvukME= =VX68 -----END PGP SIGNATURE----- --N1GIdlSm9i+YlY4t--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030718194311.GF415>