Out of date
this article is completely outdated and needs a serious overhaul, especially since the package for nfs4-utils is out-dated and doesn't include the init scripts it's supposed to.
- Done. (And nfs4-utilities now includes all necessary init scripts.) Lithis 21:03, 19 March 2009 (EDT)
I applied this article to my server today and I found an exportfs-error: in /etc/exports a range of clients has to be described like 'ip/netmask'. CORRECT WAY: '192.168.0.0/255.255.255.0', whereas the example on this page throws an error.--Zenlord 08:34, 30 September 2009 (EDT)
Merge with NFS
I'm curently making a translation of NFS. I'm planning to make a merge of the two NFS articles in it but I have to review all the information first. Once I finish the Spanish version I will update the English version. -- IR3uL 16:32, 11 February 2010 (-03:00)
Since NFSv4 is a insecure protocol (doesn't encrypt traffic), what about adding some info about tunneling it with SSH? This link is very useful: http://blogs.sun.com/shepler/entry/tunneling_nfs_traffic_via_ssh The only problem, rpcbind has to be also tunneled.
client ip address/ranges
Also mentioning that we need to put client ip address/ranges in the /etc/exports might be a good idea for people using NFS for the first time. Inxsible
Mounting the partitions on the client
I tried following the wiki but it seems that, for the client, it is no longer necessary to start rpcbind or nfs-common services.--Angheloko 11:44, 8 October 2011 (EDT)