Re: rsync experiences
"J.A. Bezemer" <email@example.com> writes:
> Playing around a bit with rsync...
> 1. rsync as shipped with slink (version 2.1.1 protocol version 19)
> NOT understand "rsync://hostname". You HAVE to use
Ah, I seem to have forgotten that and started using the URL format
throughout instead. Sorry about that. Perhaps I should have a note
pointing people to:
and explaining the equivalent format for older rsync, if they don't
want to upgrade.
> 2. "rsync hostname::" gives `root' directory listing
> "rsync --dry-run hostname::dir1/\*" gives something like a
> directory listing for subdirs
doing ``rsync hostname::'' gives the motd and a list of available
resources, doing ``rsync -av hostname::<resource>/'' gives a recursive
listing of the files available. Do I need to document this on
> 3. We have really much debian-cd rsync mirrors, and they are all
> perfectly up
> to date. NO. I tried to get the MD5SUMS files for i386:
> rsync www.uk.debian.org::debian-cd/2.1_r2/i386/MD5SUMS
> 445e235ae6ff9c6bc14e264afe0f7e96 binary-i386-1.iso
> 30a020188618a03012653f02e4bcf859 binary-i386-1.iso
This is fixed now --- they've been recovering from upgrade trauma.
Unfortunately this tends to affect many other mirrors who rsync from
them, rather than from me.
> ftp.linux.org.au seems to deny access to non-Australians
> bish.it.siu.edu is unreachable
Hm, that might be dead.
> sweat.cs.unm.edu only has 2.1_r0
True, I'll give them a kick.
> 4. But there are other rsync mirrors!
> 30a020188618a03012653f02e4bcf859 binary-i386-1.iso but it does
> NOT have the actual images!!!
They're working on it.
> ftp.funet.fi does offer anon rsync to the entire ftp archive, but
> the cd images are nowhere to be found (mirror dirs are empty)
They've moved --- it's on the web site now.
> rsync ftp.eecs.umich.edu::debian-cd/2.1_r2/i386/MD5SUMS
> 30a020188618a03012653f02e4bcf859 binary-i386-1.iso and has the
> actual images as well.
> Concluding: there are only three rsync mirrors available. There are
> also two different 2.1_r2 images. You don't get anything at all with
> the rsync commands described on cdimage.d.o.
Well the cdimage.d.o web site has been updated a couple of times
recently, so most of your points are addressed already, but any
suggestions are very welcome (I find it rather difficult to spot
things like the old rsync problem, because I'm always running the
latest, being the maintainer ;-)
> Now what does one do? Right: just FTP the entire image from
> sunsite.org.uk and be happy. Don't bother about JANET. Or anyone
> Soooo... if you want people to use rsync, it would be very nice if
> 1. cdimage.d.o was correct, in every aspect 2. there were more
> up-to-date rsync mirrors
> It seems that no one is actively doing anything about the current
> situation. Fine with me. Some plugs are ready to be pulled
> out. Permanently...?
Yeah, I've been a bit slack about updating cdimage.d.o over the last
few months, but I hope it's mostly there now. Please keep prodding me
until it's up to scratch.
P.S. for those that are wondering cdimage.d.o == cdimage.debian.org