From: "J. Bruce Fields" <bfields@fieldses.org>
To: Olaf Kirch <okir@lst.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs-utils, e_maptype
Date: Wed, 7 Mar 2007 16:28:44 -0500 [thread overview]
Message-ID: <20070307212844.GQ26553@fieldses.org> (raw)
In-Reply-To: <200703072123.47224.okir@lst.de>
On Wed, Mar 07, 2007 at 09:23:45PM +0100, Olaf Kirch wrote:
> On Wednesday 07 March 2007 03:21, J. Bruce Fields wrote:
> > Anybody know what the e_maptype export field is for? It seems to be
> > unused.
>
> IINM it goes back to the unfsd days. You could do different types of uid
> mapping there - 1:1 mapping, using NIS, or using some funky contraption called
> rpc.ugidd. Yes, we had uid mapping before NFSv4, and no, it wasnt pretty :-)
Some things are just timeless.
So does that someone somewhere could theoretically be using this code
right now? On a quick glance I'd convinced myself it was totally dead,
but I wasn't thinking about unfsd. I have no clue how it interacts with
anything else in nfs-utils.
--b.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-07 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 2:21 nfs-utils, e_maptype J. Bruce Fields
2007-03-07 20:23 ` Olaf Kirch
2007-03-07 21:28 ` J. Bruce Fields [this message]
2007-03-08 8:49 ` Olaf Kirch
2007-03-08 12:31 ` Talpey, Thomas
2007-03-08 13:28 ` Peter Åstrand
2007-03-08 13:39 ` Talpey, Thomas
2007-03-13 5:25 ` Neil Brown
2007-03-13 17:05 ` [PATCH] Remove "maptype" support J. Bruce Fields
2007-03-13 17:24 ` Peter Åstrand
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=20070307212844.GQ26553@fieldses.org \
--to=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=okir@lst.de \
/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