All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Madden <terminatorul@gmail.com>
To: util-linux@vger.kernel.org
Subject: `mount` command and POSIX Utility Syntax Guidelines
Date: Wed, 10 Oct 2012 02:28:06 +0300	[thread overview]
Message-ID: <k52bu0$1up$1@ger.gmane.org> (raw)

Hello,

I have the little annoying problem that I can not mount a DAV folder 
with the davfs2 filesystem, because I usually keep POSIXLY_CORRECT 
environment variable set. The var allows me to keep an "aliases" file 
(similar to ~/.basrc) and change it when needed if I put the file name 
in the ENV variable.

The problem is with the invocation of the mount helper command. `mount` 
will compose a command line like this:
    /sbin/mount.davfs \
           https://storage-file-eu.gmx.com/ \
           ./gmx-file-storage \
           -o rw,nosuid,nodev,noauto,user,_netdev,exec
where the option arguments ("-o rw,...") follow the operands (device, 
mount point) on the command line.

However GNU getopts() (from glibc) follows POSIX Utility Syntax 
Guidelines in this case and expects the option arguments before the 
operands.

Subsequently the mount command returns and error when mounting my DAV
folders. I am currently using a wrapper executable around mount.davfs 
that changes the order of arguments on the command line to make it work.

I hope mount command composes such a command line for historical reasons 
and that there are no hidden problems with the order of the options on 
the command line for mount helpers.

Is it please possible for mount command to be updated to change the 
order of arguments on the command line, so that it follows the POSIX 
guidelines ? At least when POSIXLY_CORRECT is set in the environment ?

I have "mount from util-linux 2.21.2 (with libblkid support)" on 
Slackware 13.37 32-bit updated with Slackware-current packages. Also 
happens on up-to-date CentOS 6.3 64-bit with updates from centosplus 
repository, that is "mount from util-linux-ng 2.17.2 (with libblkid and 
selinux support)".


See also the mount.davfs issue report at
      http://savannah.nongnu.org/support/?108145
or the issue reported on Slackware list at:
      http://comments.gmane.org/gmane.linux.slackware/4084

Thank you,
Timothy Madden


             reply	other threads:[~2012-10-09 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 23:28 Timothy Madden [this message]
2012-10-10  8:36 ` `mount` command and POSIX Utility Syntax Guidelines Karel Zak
2012-10-10 16:09   ` Timothy Madden

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='k52bu0$1up$1@ger.gmane.org' \
    --to=terminatorul@gmail.com \
    --cc=util-linux@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.