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" <autofs@vger.kernel.org>,
"samba-technical@lists.samba.org"
<samba-technical@lists.samba.org>
Subject: [fedfs-utils ANNOUNCE] Announcing the release of fedfs-utils 0.9.2
Date: Tue, 2 Jul 2013 15:13:20 -0400 [thread overview]
Message-ID: <17AC10A6-EDB2-4FD0-A0DB-A14FFC2B2BFE@oracle.com> (raw)
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.9.1:
• Packaging-related improvements
Changes since 0.9.0:
• Address build issues with recent automake and libtools
• Replace nl_langinfo(CODESET) check in command line tools
New with fedfs-utils 0.9.0:
• NSDB schema complies with latest draft standard
• DNS SRV support complies with RFC 6641
• NSDB clients support the FEDFS_SEC_TLS security type
• NSDB clients can follow LDAP referrals returned by NSDB nodes
• New tools for configuration of NSDBs
• New "display-junction" debugging command
Project web site
http://wiki.linux-nfs.org/wiki/index.php/FedFsUtilsProject
Installation guide:
http://wiki.linux-nfs.org/wiki/index.php/FedFsInstallationGuide0.9
Tarball releases:
http://git.linux-nfs.org/?p=cel/fedfs-releases.git;a=summary
Git repository:
http://git.linux-nfs.org/?p=cel/fedfs-utils.git;a=shortlog;h=refs/heads/0.9-stable
Patchwork:
http://patchwork.ozlabs.org/project/fedfs-utils/list/
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
reply other threads:[~2013-07-02 19:13 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=17AC10A6-EDB2-4FD0-A0DB-A14FFC2B2BFE@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 NNTP newsgroup(s).