From: Karel Zak <kzak@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: mount.nfs libmount support
Date: Tue, 8 Feb 2011 14:45:15 +0100 [thread overview]
Message-ID: <1297172717-26431-1-git-send-email-kzak@redhat.com> (raw)
Hi Chuck,
this is the first version of the mount.nfs with libmount support. The code
depends on the latest util-linux code from upstream git tree, or you can
wait few days for official 2.19 util-linux tarballs (and Fedora binary rpms).
I have tested:
mount.nfs server://path /mountpoint
mount.nfs server://path /mountpoint -o remount,ro
mount.nfs server://path /mountpoint -o user
umount.nfs server://path
umount.nfs /mountpoint
.. works for me. For more information see the second patch.
Karel
next reply other threads:[~2011-02-08 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 13:45 Karel Zak [this message]
2011-02-08 13:45 ` [PATCH 1/2] mount: move generic functions to utils.c and network.c Karel Zak
2011-02-08 15:43 ` Chuck Lever
2011-02-08 16:08 ` Karel Zak
2011-02-15 0:08 ` Chuck Lever
2011-02-08 13:45 ` [PATCH 2/2] mount: add --enable-libmount-mount Karel Zak
2011-02-08 15:56 ` Chuck Lever
2011-02-09 5:25 ` mount.nfs libmount support NeilBrown
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=1297172717-26431-1-git-send-email-kzak@redhat.com \
--to=kzak@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).