FC2T3 torrent locations

Matias Feliciano feliciano.matias at free.fr
Tue Apr 27 16:12:07 UTC 2004


Le mar 27/04/2004 à 17:48, Michael Stenner a écrit :
> On Tue, Apr 27, 2004 at 04:56:23PM +0200, Matias Feliciano wrote:
> > Le mar 27/04/2004 à 16:46, Jesse Keating a écrit :
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > > 
> > > On Tuesday 27 April 2004 01:13, Patrick wrote:
> > > > Very interesting that you can use rsync to update an iso to a newer
> > > > version. Just for the fun of it I did get those "slipped" iso images to
> > > > get a headstart but prefer to have the official ones. Would you by any
> > > > chance know this magical rsync command to update the early iso images to
> > > > the officially released ones?
> > > 
> > > rsync can send only the changes to files, as well as just the
> > > changed files 
> > > 
> > > IIRC.  I could be wrong though.  So if the iso names stayed the
> > > same, then only the changes would sync over, instead of the entire
> > > iso set.
> > 
> > This generally doesn't work for iso.
> > http://rsync.samba.org/tech_report/node2.html
> 
> Really?  Debian has been doing just this for several years now.  They
> (at least used to) keep a set of isos that changed with the evolving
> distro.  You could simply rsync the iso and I think it worked quite
> well.
> 

If you have two identical iso but one with an offset of one octet, then
rsync method is not efficient (it's like ftp in bandwidth usage).

Read http://rsync.samba.org/tech_report/node2.html . Generally, you
can't update an iso. You rebuild the whole iso and many files (even
identical) is not at the same place in the iso.





More information about the fedora-test-list mailing list