Re: `mount` command and POSIX Utility Syntax Guidelines

On Sun, Oct 7, 2012 at 1:29 PM, Timothy Madden <[email protected]> wrote:
> Pe 04/10/2012 01:35, Bradley D. Thornton a scris:
> [...]
>
>> On 10/02/2012 11:50 AM, Timothy Madden wrote:
>>>
>>> Hello
>>>
>>> I have a strange 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.
>>
>>
>> can't you use a script to accept your arguments and source the mounts
>> through another shell for this?
>
> [...]
>
> My arguments are those to the `mount` command, and they are right, as
> `mount` itself never complains about syntax.
>
> The problem is the command line for the `mount.davfs` helper, which is
> invoked (and composed) by `mount`.
>
> Trying to wrap the real `mount.davfs` command in a shell script was my first
> idea indeed. As I wrote in the issue report on mount.davfs2 (linked in the
> previous message) I tried that, only to find out `mount` will not invoke a
> shell script. It looks like it wants an executable as the mount helper
> command.
>
> I wrote such a simple executable (attached in the same issue report on
> mount.davfs2 tracker/list,
>  http://savannah.nongnu.org/support/download.php?file_id=26664) which I am
> currently using as my workaround, but I still think the system-provided
> `mount` command is issue at hand here, and it should follow the POSIX
> guidelines, as there may be many mount helpers out there using glibc
> getopts.

Hi Timothy, maybe I am missing some obvious constraint,
but can't you call mount.davfs or mount.davfs2 directly, with the
arguments they expect?