🚀 go-pugleaf

In article <1205@lsuc.UUCP> jimomura@lsuc.UUCP (Jim Omura) writes:
>
>     I noted the posting of 'par.c' and 'archx.c' to mod.sources recently.
>I have never used either.  Furthermore, my Unix node doesn't support
>..
>I don't like System V 'ar' format because it seems to use unprintable
>ASCII characters for something.  According to the documentation of 'archx.c',
>it doesn't.  As such, I'd like to propose usage of 'archx.c' as a standard
>archive format for OS-9'ers.

The par.c mechanism uses the BSD ar format for the file. This format,
unlike the SysV ar format, is pure ascii. i.e. if the files par'ed
together are all ascii files, the entire file is ascii.

My feelings about this are that this allows use of par'ed files on BSD
machines using ar, and BSD ar files on machines (such as my mac) using unpar.

I'm porting par/unpar to the Mac, if you care (as a single program). I
previously ported fpack to the Mac, for approximately the same use but it
doesn't support checksums.

I've ported par/unpar to a 68020 based BSD machine (which still uses the 
v7 ar for some reason), and found the checksum algorithm works there.
-- 
 Jim Budler
 Advanced Micro Devices, Inc.
 (408) 749-5806
 Usenet: {ucbvax,decwrl,ihnp4,allegra,intelca}!amdcad!jimb
 Compuserve:	72415,1200