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.8.5 released.
Date: Mon, 2 Feb 2026 06:45:30 -0500 [thread overview]
Message-ID: <fdf3631f-e924-4e4c-bd9f-db5b40a90bfe@redhat.com> (raw)
Hello,
This release contains the following:
* Man page corrections
* min-threads parameter added to nfsdctl.
* systemd updates to rpc-statd-notify.
* blkmapd not built by default (--enable-blkmapd to re-enable)
* A number of other bug fixes.
The tarballs can be found in
https://www.kernel.org/pub/linux/utils/nfs-utils/2.8.5/
or
http://sourceforge.net/projects/nfs/files/nfs-utils/2.8.5
The change log is in
https://www.kernel.org/pub/linux/utils/nfs-utils/2.8.5/2.8.5-Changelog
or
http://sourceforge.net/projects/nfs/files/nfs-utils/2.8.4/2.8.5-Changelog
The git tree is at:
git://linux-nfs.org/~steved/nfs-utils
Please send comments/bugs to linux-nfs@vger.kernel.org
steved.
next reply other threads:[~2026-02-02 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 11:45 Steve Dickson [this message]
2026-02-09 4:58 ` ANNOUNCE: nfs-utils-2.8.5 released Salvatore Bonaccorso
2026-02-14 18:28 ` Steve Dickson
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=fdf3631f-e924-4e4c-bd9f-db5b40a90bfe@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