All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Rees <rees@umich.edu>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Steve Dickson <SteveD@redhat.com>, Luk Claes <luk@debian.org>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH] mount.nfs: Preserve any explicit port=2049 option
Date: Thu, 25 Aug 2011 18:32:53 -0400	[thread overview]
Message-ID: <20110825223253.GA7607@merit.edu> (raw)
In-Reply-To: <F4AA6B6E-D029-47BC-A710-23A7AE2582A8@oracle.com>

Chuck Lever wrote:

  But we should be careful here: mount.nfs will do an rpcbind query if a
  port= was specified if there is also some doubt about whether to use TCP
  or UDP, or what NFS version is available.  The only time rpcbind queries
  should be completely squashed is when the mount parameters are specified
  completely (transport, version, and port).

Was support for SRV records ever added to either rpcbind or nfs-utils?
Wouldn't that eliminate the need for portmap at least in some cases?  I
remember Andy working on a draft for this ages ago.

  reply	other threads:[~2011-08-25 22:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-06 10:11 [PATCH] mount.nfs: Preserve any explicit port=2049 option Luk Claes
2011-08-06 17:01 ` Chuck Lever
2011-08-06 17:06   ` Luk Claes
2011-08-07 14:51     ` Chuck Lever
2011-08-25 20:25 ` Steve Dickson
2011-08-25 20:46   ` Chuck Lever
2011-08-25 22:32     ` Jim Rees [this message]
2011-08-26  0:49     ` Steve Dickson
2011-08-26 13:58       ` Chuck Lever
2011-08-27 12:56         ` Steve Dickson
2011-08-27 23:45           ` Chuck Lever
2011-08-29 14:00             ` Steve Dickson
2011-09-14 18:26 ` Steve Dickson

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=20110825223253.GA7607@merit.edu \
    --to=rees@umich.edu \
    --cc=SteveD@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=luk@debian.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 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.