From: Christoph Hellwig <hch@infradead.org>
To: "Kendrick M. Smith" <kmsmith@umich.edu>
Cc: nfs@lists.sourceforge.net, linux-fsdevel@vger.kernel.org,
nfsv4-wg@citi.umich.edu
Subject: Re: NFSv4 pseudo filesystem
Date: Fri, 10 May 2002 19:18:35 +0100 [thread overview]
Message-ID: <abh301$cra$2@main.gmane.org> (raw)
In-Reply-To: <Pine.SOL.4.44.0205101340370.27306-100000@mspacman.gpcc.itd.umich.edu>; from kmsmith@umich.edu on Fri, May 10, 2002 at 02:12:12PM -0400
On Fri, May 10, 2002 at 02:12:12PM -0400, Kendrick M. Smith wrote:
> Background: In NFSv2/v3, the server's exports are more or less independent
> of each other, and must be mounted seperately by the client. NFSv4
> introduced the requirement that the server must export a 'root filehandle'
> (which must be a directory), and that all the exports be obtainable by
> browsing the subtree rooted at the root filehandle. In other words, the
> server must present the client with ficticious directories, which live
> above the exports and serve to tie them all together into one tree. (The
> term "pseudo filesystem" is used to refer to this collection of ficticious
> directories.)
Create the NFSv4 daemons using clone(.., CLONE_NAMESPACE, ..) and build
your own per-process namespace to fit the exports.
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-05-10 18:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <message from Anton Altaparmakov on Saturday May 11>
[not found] ` <message from Kendrick M. Smith on Friday May 10>
2002-05-10 18:12 ` NFSv4 pseudo filesystem Kendrick M. Smith
2002-05-10 18:18 ` Christoph Hellwig
2002-05-10 18:18 ` Christoph Hellwig [this message]
2002-05-10 23:14 ` H. Peter Anvin
2002-05-11 6:31 ` Neil Brown
2002-05-11 6:31 ` Neil Brown
2002-05-11 17:39 ` David Chow
2002-05-11 17:39 ` David Chow
2002-05-11 20:19 ` NFS export operations question and BUG report Anton Altaparmakov
2002-05-11 20:21 ` Anton Altaparmakov
2002-05-11 21:08 ` Anton Altaparmakov
2002-05-11 21:43 ` Neil Brown
2002-05-11 23:09 ` Anton Altaparmakov
2002-05-11 21:18 ` Neil Brown
2002-05-11 22:38 ` Anton Altaparmakov
2002-05-12 7:39 ` Alexander Viro
[not found] ` <Pine.GSO.4.21.0205120330410.23398-100000@weyl.math.psu.edu >
2002-05-12 12:00 ` Anton Altaparmakov
2002-05-12 16:20 ` Jan Harkes
2002-05-13 6:54 ` Neil Brown
2002-05-10 18:12 NFSv4 pseudo filesystem Kendrick M. Smith
-- strict thread matches above, loose matches on Subject: below --
2002-05-11 0:13 Bryan Henderson
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='abh301$cra$2@main.gmane.org' \
--to=hch@infradead.org \
--cc=kmsmith@umich.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4-wg@citi.umich.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.