From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/7] Patches for nfs-utils-1.1.3
Date: Tue, 15 Jul 2008 15:30:56 -0400 [thread overview]
Message-ID: <487CFAF0.9030403@RedHat.com> (raw)
In-Reply-To: <20080630170420.9905.90111.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
Chuck Lever wrote:
> Hi Steve-
>
> Please consider these patches to be part of nfs-utils-1.1.3. They include a
> number of clean-ups, as well as support for the new "sloppy" option which
> should help automounter. Kernel support for "sloppy" is in Trond's devel
> branch now, and should be upstream in 2.6.27.
>
> The getaddrinfo(3) changes enable the mount.nfs and umount.nfs commands for
> IPv6 in the future, but should be harmless to include now. I would like to
> know if there are any problems with this before we push forward with IPv6, so
> please consider this for 1.1.3.
>
> ---
>
> Chuck Lever (7):
> text-based mount command: pass "sloppy" when -s is set
> mount command: move function to get kernel version to separate header
> mount: Introduce IPv6-aware DNS resolver API function
> nfs-utils: Add dependency for getaddrinfo(3) in configure.ac
> mount command: don't include headers multiple times
> text-based mount command: Make "internal error" message more explicit
> Python scripts: Report bandwidth in "kB/s" instead of "Kb/s"
>
>
> configure.ac | 3 ++
> tools/mountstats/mountstats.py | 8 ++--
> tools/nfs-iostat/nfs-iostat.py | 2 +
> utils/mount/Makefile.am | 2 +
> utils/mount/error.c | 7 +++-
> utils/mount/error.h | 5 +++
> utils/mount/fstab.h | 7 ++--
> utils/mount/mount.c | 18 +--------
> utils/mount/mount_constants.h | 6 ++-
> utils/mount/network.c | 78 ++++++++++++++++++++++++++++++----------
> utils/mount/network.h | 7 ++++
> utils/mount/nfs_mount.h | 6 ++-
> utils/mount/nfsmount.c | 5 +--
> utils/mount/parse_opt.h | 5 +++
> utils/mount/stropts.c | 22 ++++++++++-
> utils/mount/stropts.h | 5 +++
> utils/mount/token.h | 5 +++
> utils/mount/version.h | 51 ++++++++++++++++++++++++++
> 18 files changed, 183 insertions(+), 59 deletions(-)
> create mode 100644 utils/mount/version.h
>
All seven patches are committed...
steved.
prev parent reply other threads:[~2008-07-15 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 17:10 [PATCH 0/7] Patches for nfs-utils-1.1.3 Chuck Lever
[not found] ` <20080630170420.9905.90111.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-30 17:10 ` [PATCH 1/7] Python scripts: Report bandwidth in "kB/s" instead of "Kb/s" Chuck Lever
2008-06-30 17:10 ` [PATCH 2/7] text-based mount command: Make "internal error" message more explicit Chuck Lever
2008-06-30 17:10 ` [PATCH 3/7] mount command: don't include headers multiple times Chuck Lever
2008-06-30 17:10 ` [PATCH 4/7] nfs-utils: Add dependency for getaddrinfo(3) in configure.ac Chuck Lever
2008-06-30 17:10 ` [PATCH 5/7] mount: Introduce IPv6-aware DNS resolver API function Chuck Lever
2008-06-30 17:10 ` [PATCH 6/7] mount command: move function to get kernel version to separate header Chuck Lever
2008-06-30 17:10 ` [PATCH 7/7] text-based mount command: pass "sloppy" when -s is set Chuck Lever
2008-07-15 19:30 ` Steve Dickson [this message]
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=487CFAF0.9030403@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--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