From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <0b6901c0e0c0$22c9ff60$e8b7c6d4@SOMA> From: "Boyd Roberts" To: <9fans@cse.psu.edu> References: <20010519234657.4A6FC199C1@mail.cse.psu.edu> Subject: Re: [9fans] Re: tracking file modifiers (was: home, end ^h^j^k^l) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Date: Sun, 20 May 2001 02:02:18 +0200 Topicbox-Message-UUID: a2faa900-eac9-11e9-9e20-41e7f4b1d025 From: "Paul C Lustgarten" > Also, on the topic of managing WORM consumption, > is there some way to protect the WORM from excess > consumption, using the new muid or otherwise? a mod may never hit the worm. iirc there's a memory cache, a magnetic cache and then the worm. even munging a block only gets a new copy of the block should it hit the worm. the file-server is cleverly constructed so that only the tree and modified blocks chew up worm blocks. put the calculations in the chunk of code that burns worm blocks. > I'm thinking of scenarios such as programming mistakes > where a user accidentally writes a bunch of stuff that > they didn't intend and don't notice, or where they do > something stupid like copying over the entire project's > source tree in order to make a personal build with > a couple of modified files. you can't code against stupidity. that is the 'knife school' of design. are you sure you want to cut that?