Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!zephyr.ens.tek.com!tektronix!psueea!parsely!bucket!leonard
From: leonard@bucket.UUCP (Leonard Erickson)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: xx vs. uu
Message-ID: <1970@bucket.UUCP>
Date: 27 Feb 90 08:53:35 GMT
References: <1513@krafla.rhi.hi.is> <AUSTIN.90Feb13152915@bucsf.bu.edu> <90052.020949CMH117@psuvm.psu.edu>
Organization: Rick's Home-Grown UNIX; Portland, OR.
Lines: 26

CMH117@psuvm.psu.edu (Charles Hannum) writes:

<In article <195@falkor.UUCP>, heiby@falkor.UUCP (Ron Heiby) says:
<>
<>I have *never* had problems with zoo.  Further, I *strongly* favor
<>use of an archive format which can be manipulated on most common UNIX
<>derived systems, including both BSD and System V.  Almost all sites
<>on Usenet are running some UNIX variant and it is truly convenient to
<>be able to extract descriptive information or documentation (to be
<>printed on the shared printer) before deciding to download.

<Wrong, pal.  I'm personally running VM (as are a lot of other people I know)
<and I have at least 4 VAXen around running VMS that are also on InterNet.
<I don't have TAR (not the *nix-equivalent, anyway) or compress for VMS or VM;
<I don't have even an unZIP; I don't have LHarc; in fact, I don't have jack
<shit in the way of portable archivers for *either* system.

Zoo is available for VMS. And while you might have to mess with it a bit, 
since it is distributed in *source* form, you can port it to VM if you've
got a C compiler... I'll cheerfully mail you an MS-DOS flooppy with the
source to Zoo on it. (this is *not* an open offer, lurkers!)
-- 
Leonard Erickson		...!tektronix!reed!percival!bucket!leonard
CIS: [70465,203]
"I'm all in favor of keeping dangerous weapons out of the hands of fools.
Let's start with typewriters." -- Solomon Short