Playing around a bit with rsync...
1. rsync as shipped with slink (version 2.1.1 protocol version 19) does
NOT understand "rsync://hostname". You HAVE to use "hostname::dir1/dir2"
2. "rsync hostname::" gives `root' directory listing
"rsync --dry-run hostname::dir1/\*" gives something like a directory
listing for subdirs
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:
ftp.linux.org.au seems to deny access to non-Australians
bish.it.siu.edu is unreachable
sweat.cs.unm.edu only has 2.1_r0
4. But there are other rsync mirrors!
but it does NOT have the actual images!!!
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)
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.
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 else.
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...?