From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] linux: add config options for nfs-utils
Date: Sun, 4 Oct 2015 18:58:36 +0100 [thread overview]
Message-ID: <561168CC.9070106@mind.be> (raw)
In-Reply-To: <1436886176-118956-1-git-send-email-ryan.barnett@rockwellcollins.com>
On 14-07-15 16:02, Ryan Barnett wrote:
> When nfs-utils packages is selected, automatically enable the kernel
> options for NFSD. This will allow for an NFS server to work by only
> adding /etc/exports to the filesystem.
>
> Signed-off-by: Ryan Barnett <ryan.barnett@rockwellcollins.com>
Hi Ryan,
I've marked your patch as Rejected in patchwork. We don't want to add automatic
kernel config fiddling unless really needed for either building (e.g.
xtables-addons builds a kernel module that requires specific functions) or for
booting (e.g. systemd, ARM ABI).
In addition, in this particular case, it's possible that someone enables
nfs-utils just to be able to run rpc.statd in a nfs client that requires locking.
So instead, we think it's better to update the nfs-utils help test to mention
the Kconfig options that have to be enabled to have an NFS server.
Sorry that it had to come to a v3 and several months later before coming to
such a conclusion.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2015-10-04 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 15:02 [Buildroot] [PATCH v3 1/1] linux: add config options for nfs-utils Ryan Barnett
2015-10-04 17:58 ` Arnout Vandecappelle [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=561168CC.9070106@mind.be \
--to=arnout@mind.be \
--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