On Sat, Apr 07, 2001 at 08:00:19PM +0100, L. Cranswick wrote:
FTP and Rsync via SSH to update files - how many users do this?
I don't think I have persuaded one person to do this - they all
think it too inconvenient - too much new stuff to learn - and it
takes discipline to stick with it.
I
Hi,
I've made some progress in getting rsync to work on the .iso I'm
downloading, but now I've got another problem -- AFAICT, rsync is
re-downloading the entire file!
To recap briefly, I had downloaded an iso (mandrakefreq) using NCFTP,
but the md5sum was bad. I am hoping to use rsync to
On Sun, Apr 08, 2001 at 02:42:45PM -0400, Randy Kramer wrote:
1. rsync can't repair an iso file except by retransmitting the entire
file -- unlikely -- somebody would have told me this by now, and some of
my earlier trials produced results like:
This really depends on how the file was
On Sun, Apr 08, 2001 at 08:51:40PM +0100, M. Drew Streib wrote:
I have certainly seen large files that couldn't be "repaired" by rsync
and needed to be redownloaded.
Indeed. In this case I wonder if the original was downloaded in ASCII mode
instead of binary? That would definitely be a
Jason Haar wrote:
On Sun, Apr 08, 2001 at 08:51:40PM +0100, M. Drew Streib wrote:
I have certainly seen large files that couldn't be "repaired" by rsync
and needed to be redownloaded.
Indeed. In this case I wonder if the original was downloaded in ASCII mode
instead of binary? That
Drew,
Thanks for the response!
Very frustrating! I guess an iso consists of a mixture of binary and
ASCII data (which I've confirmed somewhat by running less on the file.
Lots of @^@^, but occasional patches of readable text. After reading
some of the description of how the rsync algorithm
Here are some possible explanations:
1) you used --partial on an earlier attempt and interrupted the
transfer. That would leave you with a partial and potentially much
smaller image locally, which would mean a subsequent transfer would
send most of the file
2) the corruption is spread
