Again, it works for me (using a pretty current FreeBSD client). The
only difference is that I never run mount_nfs directly and would use
the following command:
# mount -t nfs -o nfsv4 192.168.183.131:/home /tmp/nfs4
Assuming the client is a FreeBSD8 box on the 192.168.183.0 subnet,
I don't know why it wouldn't work, except that I'd suggest trying
the command the way I type it, in case that runs it with somewhat
different options?
rick
So, I added in /etc/rc.conf:
rpcbind_enable=YES
reboot and again typed the commands above.
and now it seems to WORK ;) :
nfs4-client# mount -t nfs -o nfsv4 192.168.183.131:/home /tmp/nfs4
nfs4-client# mount -t newnfs
192.168.183.131:/home on /tmp/nfs4 (newnfs)
nfs4-client# umount /tmp/nfs4
nfs4-client# mount -t nfs 192.168.183.131:/usr/home /tmp/nfs3
[tcp] 192.168.183.131:/usr/home: NFSPROC_NULL: RPC: Program/version
mismatch; low version = 4, high version = 4
^C
nfs4-client#
with mount_nfs command it behaves the same.
Good to know if it will work with nfsv4 server started via rc.conf and
sysctl values in sysctl.conf..
--
Marek Salwerowicz
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
