earle@MAHENDO.JPL.NASA.GOV (Greg Earle) (10/11/88)
As of October 10th, a new file (`pex.tar.Z') had replaced the previous new version of PEX (`PEX.tar.Z'). This new file is corrupted, yielding the following upon attempts at unpacking: rwxrwxr-x1641/401 0 Oct 10 17:23 1988 ./ rwxrwxrwx1641/401 0 Oct 10 17:58 1988 ./docs/ r--r--r--1641/401 9145 Oct 10 17:55 1988 ./docs/PEXclients.tex r--r--r--1641/401 30618 Oct 10 17:51 1988 ./docs/arch.tex r--r--r--1641/401 16447 Oct 10 17:51 1988 ./docs/ddpex.tex r--r--r--1641/401 17944 Oct 10 17:55 1988 ./docs/mipex.tex tar: directory checksum error (3674 != 41724) Caveat emptor. - Greg Earle Sun Los Angeles Consulting earle@Sun.COM earle@mahendo.JPL.NASA.GOV (Guest account)
joel@pyr.gatech.EDU (Joel Rives) (10/11/88)
I, too, have experienced problems with getting compressed binaries across the Internet before. Occasionally, i have found it necissary to transfer the file two or more times before an acceptable local copy is made. Please, no suggestions that i may have forgotten to set the type to binary. I'm not a novice at this. The occurances have been rare enough that i have not been that concerned. Nor do i have the time or interest in tracking down the source of this anomaly. I was quite willing assume that it might have been a problem with my local host. However, if others are experiencing the same sort of occasional failures ... well.... In any case, the only other piece to the puzzle that i have to offer is that the failures i have experienced have been with a particular file and not spread across a number of files which may have been transferred during a singel ftp session. For example, i logged into a remote host using ftp and transferred several compressed tar files. Afterwards, i uncompressed them and untarred them. One of the files was corrupt. So, i went back to the host and got that one file again. It was corrupt again. A third or fourth try produced a viable copy of the original. joel -- The thief Left it behind-- The moon at the window. -Ryokan