From: Steve Dickson <SteveD@redhat.com>
To: Jan Engelhardt <jengelh-nopoi9nDyk+ELgA04lAiVw@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: mount.nfs should support arbitrary option order
Date: Mon, 20 Oct 2008 06:54:58 -0400 [thread overview]
Message-ID: <48FC6382.3070904@RedHat.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0810182045380.17929-vVwEwcwQeYFPkBl3ERsXe1l1cybopEuJUBSOeVevoDU@public.gmane.org>
Bz https://bugzilla.linux-nfs.org/show_bug.cgi?id=170 has
been opened.. feel free to add yourself the cc list if you
would like to follow its progress.... (assuming there is any ;-) )
steved.
Jan Engelhardt wrote:
> Hi,
>
>
> currently it seems that mount.nfs only accepts -o as the last portion:
>
>
> # mount.nfs -o foo a:/ /
> usage: mount.nfs remotetarget dir [-rvVwfnsih] [-o nfsoptions]
> options:
> -r Mount file system readonly
> -v Verbose
> -V Print version
> -w Mount file system read-write
> -f Fake mount, do not actually mount
> -n Do not update /etc/mtab
> -s Tolerate sloppy mount options rather than fail
> -h Print this help
> nfsoptions Refer to mount.nfs(8) or nfs(5)
>
> # mount.nfs a:/ / -o foo
> mount.nfs: an incorrect mount option was specified
>
>
> It would be nice if options can be specified anywhere. Especially
> hard POSIX puts options first.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-10-20 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 0:46 mount.nfs should support arbitrary option order Jan Engelhardt
[not found] ` <alpine.LNX.1.10.0810182045380.17929-vVwEwcwQeYFPkBl3ERsXe1l1cybopEuJUBSOeVevoDU@public.gmane.org>
2008-10-20 10:54 ` 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=48FC6382.3070904@RedHat.com \
--to=steved@redhat.com \
--cc=jengelh-nopoi9nDyk+ELgA04lAiVw@public.gmane.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.