Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!killer!texbell!bigtex!milano!cs.utexas.edu!rutgers!mailrus!nrl-cmf!ames!amdcad!amdahl!kim From: kim@amdahl.uts.amdahl.com (Kim DeVaughn) Newsgroups: comp.sys.amiga.tech Subject: Re: zoo Message-ID: Date: 12 Oct 88 00:27:43 GMT References: <2996@amiga.UUCP> <4219@bsu-cs.UUCP> <9920@cup.portal.com> Distribution: na Organization: Amdahl Corporation, Sunnyvale, CA 94086 Lines: 28 In article <9920@cup.portal.com>, thad@cup.portal.com writes: > Besides the DELETE program/command being cognizant of file protection bits, > the COPY (and friends) are also indirectly affected (re: copying onto a file > that is read- and execute-only). In addition to preserving the "s" (script) bit, another one that Zoo (or any archiver program) should preserve is the "p" (pure) bit, which is used by the Resident command. It could be a problem, especially for inexperienced users, to figure out if this bit should be set, if it gets "lost". Granted, you don't *need* to make anything resident, but it can certainly improve the perceived performance of the system. Actually, my suggestion to Brian is to preserve *all* the protection bits in Zoo except for the "a" (archive) bit (on the presumption that when Zoo'd archive in unZoo'd, the embedded files anr now "new" to the system, and should be picked-up on the next backup run). /kim -- UUCP: kim@amdahl.amdahl.com or: {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim DDD: 408-746-8462 USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086 BIX: kdevaughn GEnie: K.DEVAUGHN CIS: 76535,25