Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!super!udel!gatech!rutgers!mailrus!iuvax!bsu-cs!dhesi From: dhesi@bsu-cs.UUCP (Rahul Dhesi) Newsgroups: comp.sys.amiga.tech Subject: Re: zoo Message-ID: <4302@bsu-cs.UUCP> Date: 13 Oct 88 12:10:10 GMT Article-I.D.: bsu-cs.4302 References: <8810121728.AA14821@cory.Berkeley.EDU> Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi) Organization: CS Dept, Ball St U, Muncie, Indiana Lines: 22 In article <8810121728.AA14821@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes: > I say, preserve them all! Real simple... It's just a longword. This could cause trouble in the future. Most of the bits are currently undefined. Suppose you store some files in a zoo archive, and zoo stores all the attribute bits as it gets them from the OS, and one of them happens to have a random value of 1. Suppose a year from now, this bit has been defined by Commodore to mean "this is a temporary file that should be deleted as soon as it is closed". When you unzoo the files then, zoo will restore all the attribute bits, and all these files will get deleted as soon as zoo finishes creating them. Or, suppose zoo forces all the currently-undefined bits to zero before storing them. But suppose Commodore happens to later assign a strange meaning to the value 0 for one of these bits. You're in trouble again. -- Rahul Dhesi UUCP: !{iuvax,pur-ee}!bsu-cs!dhesi