Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!garnet.berkeley.edu!ked
From: ked@garnet.berkeley.edu (Earl H. Kinmonth)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: SIMTEL20 to ban ARC files
Keywords: lzw, atob/btoa, 7 bit pure
Message-ID: <14564@agate.BERKELEY.EDU>
Date: 21 Sep 88 15:35:55 GMT
References: <KPETERSEN.12428752438.BABYL@SIMTEL20.ARMY.MIL> <NELSON.88Sep7224416@sun.soe.clarkson.edu> <6630@ihlpl.ATT.COM> <2736@uoregon.uoregon.edu> <8475@smoke.ARPA> <2594@csccat.UUCP> <424@pigs.UUCP> <2054@looking.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 13

In article <2054@looking.UUCP> brad@looking.UUCP (Brad Templeton) writes:
>The fact is that for the net compression is not desirable.  It clouds the

>I would suggest we use an existing format like "cpio" to do archiving.

>I would support TAR if it didn't put all files on block boundaries, which
>can be wasteful.

Yes, but this attribute makes it easier to recover at least part
of a damaged archive.  I've had to do this for both cpio and tar
archives.  The latter can usually be handled with dd and shell
loop to skip to the first valid header.  Recovering mangled cpio
archives requires a program capable of finding the "magic"
element, which may occur anywhere in a block.