Path: utzoo!mnetor!uunet!husc6!think!ames!killer!dcs!wnp From: wnp@dcs.UUCP (Wolf N. Paul) Newsgroups: comp.sources.d Subject: Re: Standard for file transmission Message-ID: <79@dcs.UUCP> Date: 8 May 88 03:16:26 GMT References: <292@cullsj.UUCP> <55@psuhcx.psu.edu> <25816@clyde.ATT.COM> <5098@chinet.UUCP> Reply-To: wnp@dcs.UUCP (Wolf N. Paul) Organization: DCS, Dallas, Texas Lines: 27 Keywords: protocol compression source In article <5098@chinet.UUCP> les@chinet.UUCP (Leslie Mikesell) writes: >In article <25816@clyde.ATT.COM> wtr@moss.UUCP (Bill Rankin) writes: >>Personally, I use cpio & compress to move files. I don't care >>about execution time, rather transmission time is my most important >I like this also, but if an entire cpio archive is compressed, it >is impossible to (a) list the directory without a decompression pass >or (b) recover any part beyond a bit error in transmission. Has >anyone condsidered a program which would leave the cpio headers >uncompressed but store the data as though each file had been individually >compressed (including adding the .Z to the name so extraction would be >possible with a normal cpio followed by uncompress)? This would be >a nice thing to use for normal backups, especially if it followed the >normal compress rules of not trying to compress something that already >had the .Z extension. That still leaves the problem of compress needing >2 extra characters in the filename and DOS needing some other name convention >entirely... Well, the sources for a cpio-compatible archiver are available from sites which archive comp.sources.unix. This archiver is called AFIO. Someone out there volunteering to add the code to do compression as suggested by Leslie? I don't think I'm qualified or I'd attempt it. -- Wolf N. Paul * 3387 Sam Rayburn Run * Carrollton TX 75007 * (214) 306-9101 UUCP: ihnp4!killer!dcs!wnp ESL: 62832882 INTERNET: wnp@DESEES.DAS.NET or wnp@dcs.UUCP TLX: 910-280-0585 EES PLANO UD