From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] rpcbind & portmap and nfs extra hints.
Date: Tue, 1 Jul 2014 20:12:11 +0200 [thread overview]
Message-ID: <20140701201211.7c84f1c3@free-electrons.com> (raw)
In-Reply-To: <B3E015034CA14BF9A830C4AE5D7E9269@JohanW7>
Dear Sagaert Johan,
On Tue, 1 Jul 2014 20:08:00 +0200, Sagaert Johan wrote:
> It seems you don't need portmap or rpcbind if you mount an nfs share with the -o onlock option.
> Without the -o nolock you need some rpc locking system like portmap or rpcbind.
>
> Should this info be put somewhere in the help of the menu options ?
I'm not really sure where it would belong to. We could indicate that in
the portmap and rpcbind help text, but it wouldn't help users trying to
do NFS mounts and not knowing about portmap/rpcbind.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-07-01 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 18:08 [Buildroot] rpcbind & portmap and nfs extra hints Sagaert Johan
2014-07-01 18:12 ` Thomas Petazzoni [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=20140701201211.7c84f1c3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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