>mount(8) says:
>
>     -o      Options are specified with a -o flag followed by a comma separat-
>             ed string of options.  The following options are available:
>
>... generic options elided ...
>
>             The options specific to NFS filesystems are described in the
>             mount_nfs(8) manual page.
> 
>But mount_nfs(8) says:
> 
>     -o      Options are specified with a -o flag followed by a comma separat-
>             ed string of options.  See the mount(8) man page for possible op-
>             tions and their meanings.

these descriptions are _NOT_ mutually incompatible.

-o to 'mount' has different meaning that '-o' to mount_nfs.

to 'mount', you say -o, then _all_ of the options you want, some of
which are mount_nfs specific and some of which are not.

to mount_nfs, you specify the mount_nfs specific options with flags,
and those which aren't mount-program-specific with -o.

> Did these options (commonly "rsize", "wsize", "timeo", "retry", et al.) get
> moved to another man page, or is it send-pr time?

these are no longer specified as words.

for instance, to mount the NFS file system foo.host:/bar on /usr/bar
read-only, with read- and write-sizes of 4096, you could do either of
the following:

mount -t nfs -o ro,-r=4096,-w=4096 foo.host:/bar /usr/bar

mount_nfs -o ro -r 4096 -w 4096 foo.host:/bar /usr/bar


there's actually an example in the mount(8) man page that elucidates
this:

             Any additional options specific to a filesystem type that is not
             one of the internally known types (see the -t option) may be
             passed as a comma separated list; these options are distinguished
             by a leading ``-'' (dash).  Options that take a value are speci-
             fied using the syntax -option=value.  For example, the mount com-
             mand:

                   mount -t mfs -o nosuid,-N,-s=4000 /dev/dk0b /tmp

             causes mount to execute the equivalent of:

                   /sbin/mount_mfs -o nosuid -N -s 4000 /dev/dk0b /tmp



cgd