From: Chuck Lever <chuck.lever@oracle.com>
To: steved@redhat.com
Cc: nfs@lists.sourceforge.net
Subject: [PATCH] Enable text-based mounts in mount.nfs
Date: Mon, 12 Nov 2007 12:46:12 -0500 [thread overview]
Message-ID: <20071112172835.3134.36815.stgit@localhost.localdomain> (raw)
Hi Steve-
Sorry for posting a single patch with a cover letter (a practice normally
frowned upon).
Here's the mount.nfs change that makes text-based NFS mounts the default,
deprecating the old legacy mount ABI for 2.6.23 kernels and later. It's
best to get this into the code base for people to start using long before
you plan to cut a new release of nfs-utils.
Text-based NFS mounts, as you know, are required to enable several upcoming
advanced NFS features, such as IPv6 support, NFS over RDMA, and local disk
caching. It will also make it simple to add support for new NFS mount
options.
The 2.6.23 kernel's text-based NFS mount support works for many basic
configurations. There are some regression nits that are cleaned up in
2.6.24.
Btw, will you continue hosting the nfs-utils git repository on
linux-nfs.org?
--
corporate: <chuck dot lever at oracle dot com>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-11-12 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 17:46 Chuck Lever [this message]
2007-11-12 17:46 ` [PATCH] mount.nfs: Time to pull the covers off text-based NFS mounts Chuck Lever
2007-11-13 15:11 ` [PATCH] Enable text-based mounts in mount.nfs 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=20071112172835.3134.36815.stgit@localhost.localdomain \
--to=chuck.lever@oracle.com \
--cc=nfs@lists.sourceforge.net \
--cc=steved@redhat.com \
/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