[Gllug] NFS across firewall

[Richard Turner]

> Mount options for nfs
>        Instead of a textual option string, parsed by the kernel, the
nfs
> file
>        system  expects  a  binary argument of type struct
nfs_mount_data.
> The
>        program  mount  itself  parses  the  following  options  of
the
> form
>        `tag=value',  and  puts  them  in  the  structure  mentioned:
> rsize=n,
>        wsize=n,  timeo=n,  retrans=n,  acregmin=n,   acregmax=n,
> acdirmin=n,
>        acdirmax=n,  actimeo=n,  retry=n,  port=n, mountport=n,
> mounthost=name,
>        mountprog=n, mountvers=n, nfsprog=n, nfsvers=n, namlen=n.   The
> option
>        addr=n  is  accepted  but ignored.  Also the following Boolean
> options,
>        possibly preceded by no are  recognized:  bg,  fg,  soft,
hard,
> intr,
>        posix, cto, ac, tcp, udp, lock.  For details, see nfs(5).
> 
> The options here for Linux include tcp as a boolean option, rather
than
> proto.
> There are therefore some differences between that and Solaris, which I
> believe I quoted earlier.  By saying check the Docs, it was not a
RTFM, it
> was take this information and build on it with what you find in the
docs
> :-)

D'oh!  I realise now that I scanned through that man page too quickly -
I didn't see 'port=n' in there.  Lucky I have such a friendly
mailing-list to post to :-)

Cheers,

Richard.


-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug