From: Karel Zak <kzak@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>, Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: mount.nfs libmount support (v3)
Date: Mon, 14 Mar 2011 14:58:26 +0100 [thread overview]
Message-ID: <1300111108-13137-1-git-send-email-kzak@redhat.com> (raw)
This is the third version of the mount.nfs with libmount support. The code
depends on util-linux >= v2.19 (e.g. Fedora 15).
v3:
- call umount_error() on mount(2) error
v2:
- move nfs_umount_do_umnt() to network.c
- use union nfs_sockaddr
- add missing GPL address paragraph
- use abstract function the storing and retrieval mount options
- use "static const" for struct option
- use "strncmp() == 0" everywhere
next reply other threads:[~2011-03-14 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 13:58 Karel Zak [this message]
2011-03-14 13:58 ` [PATCH 1/2] mount: move generic functions to utils.c and network.c Karel Zak
2011-03-14 13:58 ` [PATCH 2/2] mount: add --enable-libmount-mount Karel Zak
2011-03-21 19:04 ` mount.nfs libmount support (v3) Steve Dickson
2011-03-22 8:21 ` Karel Zak
2011-04-06 17:03 ` 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=1300111108-13137-1-git-send-email-kzak@redhat.com \
--to=kzak@redhat.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).