Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!cs.utexas.edu!uunet!philmtl!philabs!ttidca!woodside
From: woodside@ttidca.TTI.COM (George Woodside)
Newsgroups: comp.sys.atari.st
Subject: Re: ZOO and comp.binaries.atari.st
Message-ID: <4720@ttidca.TTI.COM>
Date: 10 Jul 89 12:19:22 GMT
References: <619@chyde.uwasa.fi> <2492@water.waterloo.edu>
Reply-To: woodside@ttidcb.tti.com (George Woodside)
Organization: Citicorp/TTI, Santa Monica
Lines: 19

In article <2492@water.waterloo.edu> ljdickey@water.waterloo.edu (Lee Dickey) writes:
...[edited]
>On the plus side, I think that the big advantage of ZOO is that
>one can store directory path information along with the file.

Advantages may be dis-advantages if used incorrectly. And this will be
used incorrectly.

While it is very handy to be able to store path names in the archives for your
own backup copies, it will cause a plethora of problems as soon as the disk
leaves your environment. Postings, copies of disks, backup/restore after
a change to your directory structures, and other scenarios will have lots
of new problems with either unwanted directories being created, or archive
expansion failing when paths are not found. Like most powerful tools, this
one requires great care in its use to avoid becoming the Eggplant that Ate
New York.
-- 
*George R. Woodside - Citicorp/TTI - Santa Monica, CA 
*Path:       ..!{philabs|csun|psivax}!ttidca!woodside