Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!jwt!john
From: john@jwt.UUCP (John Temples)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Antisocial ZOO behavior?
Message-ID: <1991Jan13.010644.10581@jwt.UUCP>
Date: 13 Jan 91 01:06:44 GMT
Organization: Private System -- Orlando, FL
Lines: 23

I'm not sure if this is a feature or a bug, but I found a disturbing
behavior in zoo.  If you tell zoo to do a "uM" on "*", it will delete
files which are not in the archive.  Here's an example.  Assume
"foo.zoo" contains files "bar" and "baz".

$ zoo x foo bar
Zoo:  bar            -- extracted
$ touch bar                            # do something to "bar"
$ touch xyzzy                          # create new file "xyzzy"
$ zoo uM foo *
Zoo:  bar   --  ( 0%) replaced
-----
Erasing added files...
Zoo:  bar   -- erased
Zoo:  xyzzy -- erased

File "xyzzy" was erased without being placed in the archive.  I
didn't want it in the archive; I only wanted to update files already
in the archive.  But I didn't want it erased, either.  Is this a
known problem, or is there some workaround -- or is it operator
error?
-- 
John W. Temples -- john@jwt.UUCP (uunet!jwt!john)