From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] home, end ^h^j^k^l From: nemo@gsyc.escet.urjc.es MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-rqbwfsghrwacwkksczjqdrfauf" Message-Id: <20010522071019.038B3199C1@mail.cse.psu.edu> Date: Tue, 22 May 2001 09:17:39 +0200 Topicbox-Message-UUID: a50d49a0-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-rqbwfsghrwacwkksczjqdrfauf Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit : 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). --upas-rqbwfsghrwacwkksczjqdrfauf Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <9fans-admin@cse.psu.edu> Received: from mail.cse.psu.edu (postfix@psuvax1.cse.psu.edu [130.203.4.6]) by gsyc.escet.urjc.es (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id IAA07246; Tue, 22 May 2001 08:36:33 +0200 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.16.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 0671519A04; Tue, 22 May 2001 02:36:13 -0400 (EDT) Received: from sweety.bhp.com.au (sweety.bhp.com.au [192.83.224.132]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 3084F199C1 for <9fans@cse.psu.edu>; Tue, 22 May 2001 02:35:42 -0400 (EDT) Received: from gossamer.itmel.bhp.com.au (mel01.bhp.com.au [192.83.224.17]) by sweety.bhp.com.au (8.9.3/8.9.3) with ESMTP id QAA20174 for <9fans@cse.psu.edu>; Tue, 22 May 2001 16:35:40 +1000 (EST) Received: from nc.itntl.bhp.com.au (nc.itntl.bhp.com.au [134.18.16.178]) by gossamer.itmel.bhp.com.au (8.8.8+Sun/8.8.8) with ESMTP id QAA14783 for <9fans@cse.psu.edu>; Tue, 22 May 2001 16:35:01 +1000 (EST) Received: from samarium.itntl.bhp.com.au (samarium.itntl.bhp.com.au [134.18.16.62]) by nc.itntl.bhp.com.au (8.8.6/8.8.6) with ESMTP id QAA11220 for <9fans@cse.psu.edu>; Tue, 22 May 2001 16:35:37 +1000 (EST) Received: from samarium.itntl.bhp.com.au (Sm@localhost) by samarium.itntl.bhp.com.au (8.11.3/8.11.3) with ESMTP id f4M6ZXZ02330 for <9fans@cse.psu.edu>; Tue, 22 May 2001 16:35:37 +1000 Message-Id: <200105220635.f4M6ZXZ02330@samarium.itntl.bhp.com.au> X-Authentication-Warning: samarium.itntl.bhp.com.au: Sm owned process doing -bs To: 9fans@cse.psu.edu Subject: Re: [9fans] home, end ^h^j^k^l In-reply-to: Your message of "Tue, 22 May 2001 08:25:20 +0200." <20010522061804.110E6199D7@mail.cse.psu.edu> From: Scott Merrilees Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Tue, 22 May 2001 16:35:33 +1000 >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 --upas-rqbwfsghrwacwkksczjqdrfauf--