2018-04-11 22:44 GMT+02:00 Peter J. Philipp <p...@centroid.eu>: > On Wed, Apr 11, 2018 at 10:20:37PM +0200, Paul de Weerd wrote: > > ftp doesn't do this itself, but the error detection in tcp and ssl > > (ok, so that's linked into the ftp binary) do. > > > > The file is unlikely to have been changed in flight. > > OK, odd. What I find odd is that the SHA256.sig file I got (which was > downloaded after the .iso) differs from the very first time I made contact > with ftp.eu > today with the SHA256.sig that I downloaded to verify. Could this be an > atomicity thing with the FTP mirror? >
The mirror tries to download and replace files dir-by-dir, but not edit files in-place, so its not impossible to hit the window when one of the files but not the other is replaced even if its normally a very small chance. Each snapshot is something like 100G, so there just is no way (for me) to atomically replace the lot so everything in between is a tradeoff between disk-usage, no instant writeable snaps and simplicity. -- May the most significant bit of your life be positive.
