Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!cs.utexas.edu!usc!sol.ctr.columbia.edu!eff!news.oc.com!utacfd.uta.edu!rwsys!sneaky!gordon From: gordon@sneaky.lonestar.org (Gordon Burditt) Subject: Re: Installation.. arghhhhhh!!! Message-ID: <C4KG22.9F2@sneaky.lonestar.org> Organization: Gordon Burditt References: <1obhmgINN6rv@hrd769.brooks.af.mil> <1993Mar19.121721.20041@news.cs.indiana.edu> <GENE.93Mar20083358@stark.stark.uucp> Date: Sat, 27 Mar 1993 21:08:21 GMT Lines: 22 >Yes, as a matter of fact, before ref.tfs.com was cut loose, I tried to transfer >a bunch of software that I thought might ultimately be of interest to me. >I used the .tar.Z option, and about 80% of what I transferred was corrupted. >It did not occur only on large files. One problem I noted using the .tar.Z option on ref.tfs.com is that ftp includes stderr output from tar in the data shipped. Most of the data returned began with a line like: tar: removing leading / from path names in the archive followed by the compressed data. I always managed to extract these with something like: % sh $ (read x; zcat) < ftpmail.uu | tar xvf - $ ^D % Gordon L. Burditt sneaky.lonestar.org!gordon