From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs (config) questions
Date: Fri, 13 Apr 2001 14:08:38 -0400 [thread overview]
Message-ID: <200104131808.OAA20972@smtp2.fas.harvard.edu> (raw)
yes it is possible, but not quite that easy (yet). i've done it several times,
using a specially-modified file server kernel to initialise the
bitmap for the pseudo-worm area
(after that the normal code is happy to include and write to the extended space).
is there a reason to use the pseudo-worm driver at all?
as far as i could tell, it's just making sure that blocks don't
get written twice. that's important, i guess, assuming the
cached worm driver is debugged, i'd expect to be
able to use `cw1w2' to the same effect as `cw1fw2' except
that the former doesn't have the bitmap and thus can be
lifted from one disk onto another without a special kernel.
am i missing something? (probably.)
russ
next reply other threads:[~2001-04-13 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 18:08 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-13 22:41 forsyth
2001-04-13 8:47 forsyth
2001-04-11 20:20 Axel Belinfante
2001-04-12 19:44 ` Axel Belinfante
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=200104131808.OAA20972@smtp2.fas.harvard.edu \
--to=rsc@plan9.bell-labs.com \
--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).