From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] user-level file systems for Linux
Date: Wed, 18 Feb 2004 21:58:00 -0700 [thread overview]
Message-ID: <Pine.LNX.4.44.0402182153390.27316-100000@maxroach.lanl.gov> (raw)
In-Reply-To: <20040219101557.035de8f0.martin@parvat.com>
On Thu, 19 Feb 2004, Martin C.Atkins wrote:
> On Wed, 18 Feb 2004 20:57:42 -0500 "Russ Cox" <rsc@plan9.bell-labs.com> wrote:
> >...
> > Actually there have been a handful of projects doing
> > similar things over the past few years, and they've all
> > died out. I'm optimistic about FUSE because it's almost
> > an exact translation of the VFS layer, meaning that it's
> > simple and as expressive as possible.
> >
> > Russ
>
> I wrote a user-mode filesystem for Linux just yesterday. In Python
> (using a library I hacked up early last year). Works great. One of these days
> I'll get around to packaging it up, and releasing it, if people are
> interested.
w.r.t. these things and 9p2000: it seems to me there are ops in the Linux
VFS that can not be expressed in 9p2000. Three that come to mind are
symlinks, hard links, and extended attributes (used for ACLs). The Linux
inode fields have some things that 9p2000 doesn't have, and vice-versa.
I had to add hard link/symlink ops to my 9p2000 to make things work as
expected on linux (else users will get mad). So I got several more ops for
things I really did not want to add, but had to.
I'm not sure I see how 9p2000 could support everything that FUSE would
want to do. Take a look inside any existingt NFS client/server to see how
really crazy it gets once named pipes, device nodes, etc. start to creep
in.
The goal of using 9p2000 with these things may require some difficult
decisions ... possibly the easiest thing to do is learn NFS V4 :-(
ron
next prev parent reply other threads:[~2004-02-19 4:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 1:57 Russ Cox
2004-02-19 2:19 ` boyd, rounin
2004-02-19 2:20 ` ron minnich
2004-02-19 2:35 ` boyd, rounin
2004-02-19 4:45 ` Martin C.Atkins
2004-02-19 4:58 ` ron minnich [this message]
2004-02-19 9:20 ` Charles Forsyth
2004-02-19 14:46 ` ron minnich
2004-02-19 14:50 ` boyd, rounin
2004-02-19 14:57 ` Stephen Wynne
2004-02-19 3:10 YAMANASHI Takeshi
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=Pine.LNX.4.44.0402182153390.27316-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--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).