Re: [9fans] home, end ^h^j^k^l

[nemo@gsyc.escet.urjc.es]

[-- Attachment #1: Type: text/plain, Size: 508 bytes --]

:  Then what do you do when the same file is created again?
:  Associate all the old info with the new file?
:  Rename the old file?  How do you handle collisions?

Just keep the last entry for a given name (deleted or not).  If the
file is created again, you could forget about the last deleted
directory entry w/ the same name. After all, you couldn't tell if the
file was just `modified' and the change was to rewrite it all. (Ok, you
can tell, but for the application it would be the same).



[-- Attachment #2: Type: message/rfc822, Size: 2657 bytes --]

From: Scott Merrilees <Sm@itntl.bhp.com.au>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] home, end ^h^j^k^l
Date: Tue, 22 May 2001 16:35:33 +1000
Message-ID: <200105220635.f4M6ZXZ02330@samarium.itntl.bhp.com.au>

>nemo@gsyc.escet.urjc.es:
>The directory entry could be kept allocated like a zombie. disk space
>is cheap.  Of course this only handles the top of a deleted hierarchy,
>but for the purposes of knowing who deleted what it may suffice.

Then what do you do when the same file is created again?
Associate all the old info with the new file?
Rename the old file?  How do you handle collisions?

If you really want to know who deleted a file, wouldn't it be easier to
just maintain a log somewhere?

Sm