Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!ncrlnk!emdeng!btrue
From: btrue@emdeng.Dayton.NCR.COM (Barry.True)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Binaries and which packing (Was Re: xx vs. uu)
Message-ID: <225@emdeng.Dayton.NCR.COM>
Date: 16 Feb 90 13:51:23 GMT
References: <1513@krafla.rhi.hi.is> <1990Feb14.134810.8305@uwasa.fi> <1745@borabora.omni.com>
Reply-To: btrue@emdeng.UUCP (Barry.True)
Organization: NCR, E&M Dayton
Lines: 39

In article <1745@borabora.omni.com> bob@omni.com (Bob Weissman) writes:
>
>I beg to differ.  I don't have extensive experience with zip, and none
>with lzh, but zoo is the first archiver I've seen which lets you pack an
>entire directory hierarchy with one command, and unpack it into the same
>hierarchy with one command.  This is real useful.  You just have to forget
>the "novice" commands and learn the "expert" commands.  Rahul's extensive
>Unix-style manual page makes this easy.
>

Version 1.01 of PKZIP/PKUNZIP also allows packing/unpacking an entire
directory heirarchy. However it still does suffer from the fact that you
can't zip files on UNIX, only unzip them.

I thought the whole crux of the matter was not which archiving system to
use but which ENCODING/DECODING system to use? On most UNIX systems that
I've worked with you can't transmit binary data over regular mail lines.
That is why they had to be encoded at the source end and decoded at the
target end. This is the case here.

Since most of the PD archiving packages are available for a small fee
(i.e., < $5 from shareware/PD distributors) or free over then NET or
from FTP sites, and since there are also PD utilities to convert from one
archive format to another (Arcmaster comes to mind since I'm currently
using it! :^>), what is the real issue? I know that many of you have said
that you want to unPAK/ZIP/ZOO/WHATEVER the archives on the UNIX system
before transferring them to your PC but is that an absolute requirement?
Maybe I'm ignorant here and, if I am, someone please let me know. What
kind of file transfer methods are being used to transfer the files from
UNIX boxes to PCs out on the NET? Currently we have PCs and UNIX systems
set up on a LAN and use a binary file transfer method to get and send
files to an from the UNIX system we want. Since we also have remote
login capability we can do all the necessary processing directly from
our PCs. It seems that even if you don't have this type of setup it would
be easier to transfer one archive file from the UNIX system to a PC than a
whole bunch of smaller binaries after de-archiving them on the UNIX box. As
I said before, if there is something I'm overlooking, please let me know.

procedures