Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!texbell!vector!chip From: chip@vector.Dallas.TX.US (Chip Rosenthal) Newsgroups: comp.sources.d Subject: Re: Why "shar: Shell Archive (v1.22)" is bad Message-ID: <755@vector.Dallas.TX.US> Date: 26 Sep 89 20:18:35 GMT References: <14502@bloom-beacon.MIT.EDU> <4155@cbnewsh.ATT.COM> <495@crdos1.crd.ge.COM> Reply-To: chip@vector.Dallas.TX.US (Chip Rosenthal) Organization: Dallas Semiconductor Lines: 20 In article <495@crdos1.crd.ge.COM> davidsen@crdos1.UUCP (bill davidsen) writes: > The default behavior of shar2 (up to v1.25 now) is to break up the >total collection of data into M files of size S each. As others have asked, I'd also like to see the feature which checks that parts 1 through N-1 have been processed before part N is removed. Here is the scenario. I have an 8-part shar archive compressed and stored in Part1.Z through Part8.Z. I want to unshar it, using my "safe unshar" program. So I say: % foreach file ( /archive_dir/Part?.Z ) zcat $file | unshar end Braphz. Outa luck. Parts 2 through 8 won't extract because the required stuff isn't in the directory where the unshar happens. -- Chip Rosenthal / chip@vector.Dallas.TX.US / Dallas Semiconductor / 214-450-5337 Someday the whole country will be one big "Metroplex" - Zippy's friend Griffy