From: Petr Vorel <petr.vorel@gmail.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/nfs-utils: bump version to 2.8.1
Date: Mon, 4 Nov 2024 22:16:55 +0100 [thread overview]
Message-ID: <20241104211655.GA1423113@pevik> (raw)
In-Reply-To: <20241104202319.2193487-1-giulio.benetti@benettiengineering.com>
Hi Giulio,
Thanks for the update!
> * disable junction and nfsdctl by default
...
> NFS_UTILS_CONF_OPTS = \
> --enable-tirpc \
> --enable-ipv6 \
> + --disable-junction \
> + --disable-nfsdctl \
> --without-tcp-wrappers \
> --with-statedir=/run/nfs \
> --with-rpcgen=$(HOST_DIR)/bin/rpcgen
> @@ -30,6 +32,8 @@ HOST_NFS_UTILS_CONF_OPTS = \
> --disable-gss \
> --disable-uuid \
> --disable-ipv6 \
> + --disable-junction \
> + --disable-nfsdctl \
> --without-tcp-wrappers \
> --with-statedir=/run/nfs \
> --disable-caps \
What was the reason to disable them? Shouldn't be at least nfsdctl enabled?
man nfsdctl(8) "control program for the Linux kernel NFS server" [1]
That sounds useful.
man nfsref(8) "manage NFS referrals"
...
A junction is a file system object on an NFS server that, when an
NFS client encounters it, triggers a referral. Similar to a
symlink, a junction contains one or more target locations that
the server sends to clients in the form of an NFSv4 referral.
I'm not sure how much useful this is, but it's enabled by default. Also Debian
explicitly enables it. Do we have a good reason to disable it?
> * drop 2 local patches that have been committed.
Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
Kind regards,
Petr
[1] https://manpages.debian.org/testing/nfs-kernel-server/nfsdctl.8.en.html
[2] https://man7.org/linux/man-pages/man8/nfsref.8.html
[3] https://salsa.debian.org/kernel-team/nfs-utils/-/blob/master/debian/rules?ref_type=heads
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-11-04 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 9:07 [Buildroot] [PATCH] package/nfs-utils: bump version to 2.7.1 Giulio Benetti
2024-10-26 20:13 ` Thomas Petazzoni via buildroot
2024-11-04 20:23 ` [Buildroot] [PATCH] package/nfs-utils: bump version to 2.8.1 Giulio Benetti
2024-11-04 21:16 ` Petr Vorel [this message]
2024-11-04 21:40 ` Giulio Benetti
2024-12-29 21:20 ` Thomas Petazzoni via buildroot
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=20241104211655.GA1423113@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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