From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: tracking file modifiers (was: home, end ^h^j^k^l)
Date: Sun, 20 May 2001 02:02:18 +0200 [thread overview]
Message-ID: <0b6901c0e0c0$22c9ff60$e8b7c6d4@SOMA> (raw)
In-Reply-To: <20010519234657.4A6FC199C1@mail.cse.psu.edu>
From: "Paul C Lustgarten" <plus@cosym.net>
> 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?
next prev parent reply other threads:[~2001-05-20 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 23:46 Paul C Lustgarten
2001-05-20 0:02 ` Boyd Roberts [this message]
2001-05-20 3:12 ` [9fans] Worm consumption (was: Re: tracking file modifiers) Martin Harriss
2001-05-20 3:17 ` Boyd Roberts
2001-05-20 0:10 [9fans] Re: tracking file modifiers (was: home, end ^h^j^k^l) rob pike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='0b6901c0e0c0$22c9ff60$e8b7c6d4@SOMA' \
--to=boyd@planete.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).