www-mirrors mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jason andrade <ja...@dstc.edu.au>
Subject Re: [qmirror] steps towards better mirroring
Date Sun, 14 Jan 2001 02:25:42 GMT
On Sat, 13 Jan 2001, Brian Behlendorf wrote:

> Care would be taken to make sure that only the most recent versions of any
> particular branch of the code line would be there, as well as only the
> most recent binary builds.  E.g, today, under /dist/httpd-2.0/, we'd have
> apache-2.0a9, and *perhaps* 2.0a8, but older ones would be shuffled off to
> httpd.apache.org/dist/ and perhaps further under a /dist/old or something.  
> This is to try and keep low the total amount of disk space needed to
> mirror the apache.org distributables.

i think it's a good idea to shuffle it to dist/old, but if there's a way
to do this better for rsync, can we implement.

the reason i ask is.. if you create a /old, then mirror sites can easily
decide to exclude this to save space.. *but*.. for sites that do carry
it.. it is quite `expensive' in bandwidth when.

previous releases is 2.0a7
current release is 2.0a8
new release comes out is 2.0a9

everything in 2.0a7 gets moved to old/

rsync looks. deletes the entire 2.0a7 tree.  then refetches it into old/2.0a7

not great sense.. and apart from manually letting mirrors know (which then
isn't automatable).. 


i've had this discussion with a number of linux vendors on their ISO image
distributions and some have now fixed it.. e.g instead of releasing their
ISO as linux-release-1.0 and then updating the filename to 1.0.1 (which
results in a deletion of 650M object and refetch), they call the filename
linux-release.iso and symlink versions to it.  is something similar possible
with apache dist binary trees ?


-jason


Mime
View raw message