From: "Chao-Kuo Lin" <chaokuo@iname.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Software release: divergefs
Date: Thu, 4 Aug 2005 16:58:22 -0500 [thread overview]
Message-ID: <20050804215822.46F3A1F50B1@ws1-2.us4.outblaze.com> (raw)
Inspired by various discussions about the utility of a
layer/union/overlay/stitch file system, I wrote one as a project
for the Operating System Practicum class here at CMU. It supports
the simple case of making a few mutations "above" a read-only base
file system tree, and also allows storing files in various layers
above the base (so, for example, you can store object files in
local RAM instead of writing them back to a distant file server).
It's done enough that you can use it to build kernels and the like,
but the user interface is very rough--probably just enough so that
people can complain about it and help figure out what the right
interface would be.
It's available at
http://www.cs.cmu.edu/~412-s04/chaokul/divergefs.tar.gz
with Wiki entry at
http://www.cs.bell-labs.com/wiki/plan9/divergefs/
Bug reports, comments, and suggestions welcome.
Chao-Kuo Lin
--
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
reply other threads:[~2005-08-04 21:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050804215822.46F3A1F50B1@ws1-2.us4.outblaze.com \
--to=chaokuo@iname.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).