From: Olga Kornievskaia <aglo@umich.edu>
To: linux-nfs <linux-nfs@vger.kernel.org>
Subject: why no nlmport mount option been implemented
Date: Mon, 4 Feb 2019 13:54:47 -0500 [thread overview]
Message-ID: <CAN-5tyEm3F2Z8bJ_SyLdWqj432xy4_+W0ucMBpOg5PV0u5OGWw@mail.gmail.com> (raw)
Hi folks,
I'm curious why there is an option to by-pass the port mapper call for
the MNT port but not for the NLM port? Is there a reason why having
such an option is a bad idea?
Thank you.
reply other threads:[~2019-02-04 18:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAN-5tyEm3F2Z8bJ_SyLdWqj432xy4_+W0ucMBpOg5PV0u5OGWw@mail.gmail.com \
--to=aglo@umich.edu \
--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;
as well as URLs for NNTP newsgroup(s).