From: Bruce Fields <bfields@fieldses.org>
To: Steve Dickson <SteveD@RedHat.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH RFC 0/3] Add server-side support for junctions to nfs-utils
Date: Thu, 11 Jan 2018 10:17:38 -0500 [thread overview]
Message-ID: <20180111151738.GB4839@fieldses.org> (raw)
In-Reply-To: <d3a5175c-a330-ac7a-67ed-19cfc5363ec1@RedHat.com>
On Thu, Jan 11, 2018 at 09:20:54AM -0500, Steve Dickson wrote:
> On 01/10/2018 02:42 PM, Chuck Lever wrote:
> > I don't have any quarrel with carving out the non-network-exposed
> > functionality of mountd and putting it in an upcall similar to
> > nfsidmap. Seems like an entirely separate project, though, and
> > probably a significant chunk of work.
> It is... I was just floating the idea.
Yeah, I don't mean to veto the idea, I think we've discussed it before
and it's kind of appealing. I just think we haven't thought it through
and we don't have any real reason it's necessary right now. I'd hate to
send someone down that rabbit hole and have the come back with a bunch
of work and us say "uh, but why do we want this?".
--b.
prev parent reply other threads:[~2018-01-11 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 21:49 [PATCH RFC 0/3] Add server-side support for junctions to nfs-utils Chuck Lever
2018-01-08 21:50 ` [PATCH RFC 2/3] Add LDAP-free version of libnfsjunct " Chuck Lever
2018-01-08 21:50 ` [PATCH RFC 3/3] Add 'nfsref' command Chuck Lever
2018-01-09 19:21 ` [PATCH RFC 0/3] Add server-side support for junctions to nfs-utils J. Bruce Fields
2018-01-09 19:36 ` Chuck Lever
2018-01-10 17:13 ` Steve Dickson
2018-01-10 17:17 ` Bruce Fields
2018-01-10 17:26 ` Steve Dickson
2018-01-10 17:36 ` Bruce Fields
2018-01-10 19:42 ` Chuck Lever
2018-01-11 14:20 ` Steve Dickson
2018-01-11 15:17 ` Bruce Fields [this message]
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=20180111151738.GB4839@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@RedHat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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