PS: Forgot to mention, I searched the archives since September 2000 -- but found nothing to help me. (Search was by visual scan of threads, then calling up promising posts. Found some stuff about raw disk images (in October, IIRC), something about RedHat in Jan, and a question (but no answers) about Debian in March. I've also been through help, man, and info, and several tutorials. Thanks, Randy Kramer
Can rsync fix a MandrakeFreq iso with a bad md5sum? (Without re-downloading the entire file?) How? (See my problems, below.) I have rsync 2.3.2 protocol version 21 (Mandrake 7.0) on my preferred download box (cdburner). I could use rsync 2.4.6 protocol version 24 on my workstation, if I resize some partitions to store two copies of the iso on one partition. In other words, I'd rather stick with 2.3.2 unless it will not do the job. I downloaded MandrakeFreq-i586-20010316.iso from Penn State (carroll.cac.psu.edu) using ncftp. After downloading I checked the md5sum and found it incorrect. I'm hoping to use rsync to correct it. I've read the man pages and visited some web sites, but I've had and am still having some trouble using rsync. (Alexander Skwar from the mandrake cooker list helped me with some of the problems -- thanks!) Now when I use rsync, I get reports like the following, but the md5sum does not change (it is still wrong): At least 4 tries so far. First 2 tries, I used no options, just: rsync carroll.cac.psu.edu::mandrake-iso/mandrakefreq-i586-20010316.iso mandrakefreq-i586-20010316.iso (the pwd is set to the location of the original downloaded file) Results: wrote 105 bytes read 85 bytes 20.00 bytes/sec total size is 684400640 speedup is 3602108.63 But the md5sum was still bad. Next 2 tries, I ran it with -avz options. Results: On these two tries I got two additional lines, followed by two lines very much like the results from the first trial: receiving file list ... done chown mandrakefreq-i586-2001-0316.iso : Operation not permitted wrote 105 bytes read 85 bytes 20.00 bytes/sec total size is 684400640 speedup is 3602108.63 (PS: The lines above were typed in, not cut and pasted. In the real results, the last two lines are not identical but always slightly different -- different numbers of bytes read and written.) The md5sum still has not changed. Fifth try: I just tried it again with --partial and --verbose, and got two lines like my first result, still no change in the md5sum. I've also posted some questions on the rsync faq-o-matic, but, for the last two days I can't get back to it -- seems like they have a problem. Should rsync work to solve this problem? How? Is there any chance the md5sum posted at carroll is wrong? This is the md5sum I get each time: f1a03f8a2b4637dc5299ce1b85a62c08 Thanks, Randy Kramer
