public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 10 Jan 2018 12:36:56 -0500	[thread overview]
Message-ID: <20180110173656.GC26882@fieldses.org> (raw)
In-Reply-To: <a1d86617-608c-c4bc-6f96-c5deff60c7fb@RedHat.com>

On Wed, Jan 10, 2018 at 12:26:10PM -0500, Steve Dickson wrote:
> 
> 
> On 01/10/2018 12:17 PM, Bruce Fields wrote:
> > On Wed, Jan 10, 2018 at 12:13:39PM -0500, Steve Dickson wrote:
> >>
> >>
> >> On 01/09/2018 02:36 PM, Chuck Lever wrote:
> >>>
> >>>
> >>>> On Jan 9, 2018, at 2:21 PM, bfields@fieldses.org wrote:
> >>>>
> >>>> Thanks for doing this!  I may not get the chance to do a real review,
> >>>> but I'm in favor of the basic idea.
> >>>
> >>> How do you feel about building support for junctions into mountd,
> >>> and getting rid of the libnfsjunct DLL ?
> >> I would rather not put new functionality in daemons that needs rpcbind.
> >> With the idea of, someday, having clean v4-only configuration
> >> (aka no mountd, statd, or lockd).  
> > 
> > rpc.mountd is used by v4 for a lot of stuff already, so it's not going
> > away.  
> Understood.... I guess I'm looking for a way to replace it with
> a command the kernel can call to only do v4 stuff.
> Would something like that make sense?

It would be a fair amount of work and I don't think there's a strong
reason to do it.

rpc.mountd -N2 -N3 should do what we want.

--b.

> 
> > Is it trying to register with rpcbind in the case it's called
> > with -N2 -N3?  That would be a bug.
> Looking at the code... probably not... 
> 
> steved.
> > 
> > --b.
> > 

  reply	other threads:[~2018-01-10 17:36 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 [this message]
2018-01-10 19:42       ` Chuck Lever
2018-01-11 14:20         ` Steve Dickson
2018-01-11 15:17           ` Bruce Fields

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=20180110173656.GC26882@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