From: Chuck Lever <chuck.lever@oracle.com>
To: "fedfs-utils;release announcements"
<fedfs-utils-announce@oss.oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
autofs@vger.kernel.org, samba-technical@lists.samba.org
Subject: Announcing the release of fedfs-utils version 0.10.4
Date: Wed, 8 Jul 2015 14:14:11 -0400 [thread overview]
Message-ID: <CE28D97A-7F26-4ED6-B0BE-53F3E988E6F9@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]
This package contains an implementation of the Federated Filesystem
(FedFS) Proposed Standard for Linux. For an introduction to FedFS, see
RFC 5716.
This is an ALPHA quality release. The code in this release is not
guaranteed to work. Programming, administrative, and user interfaces
may change significantly before the next release. This release is for
technology preview only.
Changes since 0.10.3:
• Fix bugs in admin tools
Changes since 0.10.2:
• More error handling fixes
• Remove an incorrect package dependency
Changes since 0.10.1:
• Fix bugs in nsdb-jumpstart
• Numerous fixes to error handling paths
• Introduce basic support for Coverity analysis
Changes since 0.10.0:
• Address packaging issues
New with fedfs-utils 0.10.0:
Non-backwards compatible changes:
• *ldaperr removed from libnsdb API
• ADMIN client tools no longer use AUTH_NONE security
• ADMIN client tools no longer exit with FedFS status code
New features:
• Python package PyFedfs added
• Tool for configuring FedFS domain root directories
• Tool for setting up NSDBs using OpenLDAP
• Simpler NCE discovery (compliant with new FedFS NCE I-D)
• admin_t API for performing remote ADMIN requests
• rpc.fedfsd uses an ACL to control who can perform ADMIN requests
• rpc.fedfsd and ADMIN tools support RPCSEC and Kerberos v5
Minor fixes:
• FEDFS_LOOKUP_JUNCTION no longer returns NSDB_LDAP_VAL
• fedfs-map-nfs4 handles multiple SRV records
• Packaging simplifications
• Dozens of code clean-ups and bug fixes; consult Changelog for details
Source code available at:
http://git.linux-nfs.org/?p=cel/fedfs-utils.git;a=log;h=refs/heads/0.10-stable
The new head of the 0.10-stable branch is commit:
da0e25b59275 Release 0.10.4
Patchwork available at:
http://patchwork.ozlabs.org/project/fedfs-utils/list/
Tarball releases available at:
http://git.linux-nfs.org/?p=cel/fedfs-releases.git;a=summary
--
Chuck Lever
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
reply other threads:[~2015-07-08 18:14 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=CE28D97A-7F26-4ED6-B0BE-53F3E988E6F9@oracle.com \
--to=chuck.lever@oracle.com \
--cc=autofs@vger.kernel.org \
--cc=fedfs-utils-announce@oss.oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=samba-technical@lists.samba.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).