From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: ANNOUNCE: nfs-utils-2.9.1 released.
Date: Sat, 4 Apr 2026 16:43:46 -0400 [thread overview]
Message-ID: <955a922e-c12d-435b-a698-caf73312f01d@redhat.com> (raw)
Hello,
This release contains a minor version being disabled
(which is why the minor release was bumped),
new features and a bug fix:
* V4.0 is turned off on the servery by default
* netlinx is now used for upcalls in exportfs, exportd, mountd
* signed filehandle support was added.
* nfsdctl now checks for listeners before starting.
The tarballs can be found in
https://www.kernel.org/pub/linux/utils/nfs-utils/2.9.1/
or
http://sourceforge.net/projects/nfs/files/nfs-utils/2.9.1
The change log is in
https://www.kernel.org/pub/linux/utils/nfs-utils/2.9.1/2.9.1-Changelog
or
https://sourceforge.net/projects/nfs/files/nfs-utils/2.9.1/2.9.1-Changelog
The git tree is at:
git://linux-nfs.org/~steved/nfs-utils
Please send comments/bugs to linux-nfs@vger.kernel.org
steved.
reply other threads:[~2026-04-04 20:43 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=955a922e-c12d-435b-a698-caf73312f01d@redhat.com \
--to=steved@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).