Regarding option parsing by new nfs utils package

[Kevin Coffman]

Sorry for the delay in responding.  Can you be more specific regarding
what is failing or what is puzzling you?

# /bin/mount -t nfs4 SERVER:/  /mnt/clnt

and

# /sbin/mount.nfs4 SERVER:/ /mnt/clnt -t nfs4

should produce the same results.  (Yes, the order of the parameters is
different.)

If either is failing, can you give the error messages you see?

On 4/26/07, vidyasagar Ravipati <vidya.chowdary at gmail.com> wrote:
> I am trying to look into source code for mount in nfs utils package and
> while during playing with couple of options , I puzzled by the option
> parsing issue.
>
> Normal "mount" command which came with linux kernel works fine with nfs4
> option when I specified in the following format
> "mount -t nfs4 SERVER:/  /mnt/clnt "
>
> But when I am trying mount using the binary "mount.nfs4" in the similar
> fashion, it fails.
>
> mount.nfs4 SERVER:/mnt/srvr  /mnt/clnt -t nfs4
> mount.nfs4 SERVER:/  /mnt/clnt -t nfs4
> It puzzles me a lot , is the binary "mount.nfs4" which is built from the
> package nfs-utils-1.0.10 option parsing is different or
> whether I am sepcifying the wrond argument format for this binary to mount
> nfs4 or is it a bug.
> Can anyone clarify with an example if mount.nfs4 binary works with nfs4
> option fine  and it would be a great help.
> --
> Vidya Sagar Chowdary Ravipati
> M.S.Student,
> Computer Science Department
> Stony Brook University
> Stony Brook-11790
>
>
>
> _______________________________________________
> NFSv4 mailing list
> NFSv4 at linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4
>