From: Prem Karat <prem.karat@linux.vnet.ibm.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] nfs-utils: Don't hard code source and destination args
Date: Tue, 28 Jun 2011 22:29:54 +0530 [thread overview]
Message-ID: <20110628165954.GA13059@d6fc318.ibm.com> (raw)
In-Reply-To: <FA506314-750E-4E20-B80C-B507D032D962@oracle.com>
On 06/28/11 12:02pm, Chuck Lever wrote:
>
> On Jun 28, 2011, at 6:41 AM, Prem Karat wrote:
>
> >
> > Currently souce and destination parameters should be passed as first and
> > second paramter while using mount.nfs. This patch allows them to be passed
> > anywhere while mounting.
> >
> > Current functionality is
> > mount.nfs source destn -o <options>
> > This patch will allow to do this
> > mount.nfs -o <options> source destn
> > or
> > mount.nfs -o <options> source -o <options> destn
>
> Yep, that's clear, but why is this desirable? mount.nfs should be invoked only by the mount command. It's not meant to be run by humans.
Bare with me if my understanding is incorrect, however the man page does say that
it can be used as a standalone command with limited functionality.
Also it makes sense to use it if a newbie wants to know the nfs specific
options. The mount.nfs command shows a pointer to the correct man page for
nfs specific options.
Cheers,
Prem
next prev parent reply other threads:[~2011-06-28 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 10:41 [PATCH 1/1] nfs-utils: Don't hard code source and destination args Prem Karat
2011-06-28 16:02 ` Chuck Lever
2011-06-28 16:59 ` Prem Karat [this message]
2011-06-28 17:29 ` Steve Dickson
2011-06-28 17:49 ` Chuck Lever
2011-06-28 17:59 ` Luk Claes
2011-06-28 18:33 ` Chuck Lever
2011-06-29 14:28 ` Steve Dickson
2011-06-29 23:09 ` NeilBrown
2011-06-30 10:58 ` Steve Dickson
2011-06-30 11:10 ` NeilBrown
2011-06-30 11:19 ` Steve Dickson
2011-06-30 17:40 ` J. Bruce Fields
2011-07-01 20:04 ` Steve Dickson
2011-07-01 20:56 ` J. Bruce Fields
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=20110628165954.GA13059@d6fc318.ibm.com \
--to=prem.karat@linux.vnet.ibm.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).