From: Jamie Lokier <jamie@shareable.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Steve French <smfrench@austin.rr.com>, linux-fsdevel@vger.kernel.org
Subject: Re: filesystem client mapping of uid_t/gid_t field in lookup
Date: Sat, 14 May 2005 12:38:57 +0100 [thread overview]
Message-ID: <20050514113857.GA19653@mail.shareable.org> (raw)
In-Reply-To: <1116052679.13863.38.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> In NFSv4 (which is the only NFS implementation that supports native
> uid/gid mapping since it defines a globally unique username/groupname
> space for use on the wire) the uid/gid mapping is done using upcalls to
> a userland daemon on both the client and server side. A cache is used in
> order to avoid too many upcalls. Why would this sort of approach be
> impractical for CIFS?
It would be even nicer if they could share the same mapping daemon.
-- Jamie
next prev parent reply other threads:[~2005-05-14 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 22:50 filesystem client mapping of uid_t/gid_t field in lookup Steve French
2005-05-14 6:37 ` Trond Myklebust
2005-05-14 11:38 ` Jamie Lokier [this message]
2005-05-15 22:37 ` Steve French
2005-05-16 18:18 ` Bryan Henderson
2005-05-16 19:03 ` Spencer Shepler
2005-05-16 22:23 ` Trond Myklebust
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=20050514113857.GA19653@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=smfrench@austin.rr.com \
--cc=trond.myklebust@fys.uio.no \
/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