Works for me. I did a little looking and it the only other place I can find NFS documented is in the kubuntu networking guide. The section on NFS mostly points to documents in the community wiki, so I guess in my opinion it makes sense to give a little heads up about the client. Anyway, here's a new diff with the changes. <div>On 9/13/07, Mathias Gug <<a href="mailto:mathiaz@ubuntu.com">mathiaz@ubuntu.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Adam, On Wed, Sep 12, 2007 at 10:20:02PM -0400, Adam Sommer wrote: > Yes, it gets installed on the server. But from my tests if portmap isn't > installed and running on the client you can't mount an NFS share. My log > starts filling up with entries such as: > > Sep 12 13:43:20 Grizzlebees kernel: [44217633.150000] portmap: server > localhost not responding, timed out > Sep 12 13:43:20 Grizzlebees kernel: [44217633.150000] RPC: failed to contact > portmap (errno -5). > Sep 12 13:43:20 Grizzlebees kernel: [44217633.170000] lockd_down: no lockd > running. > Sep 12 14:03:33 Grizzlebees kernel: [44218846.010000] ppdev: user-space > parallel port driver Hum... You're correct when you say that you need the portmapper running on the client. However it should be installed and started by default when you install nfs-common (which contains the nfs client). > But since the guide is about the server side maybe it doesn't need to be > covered? I was just thinking that when I was following the example I didn't > have portmap on my client...either way. It may worth adding a note about it: "In case nfs mounting doesn't work, make sure that the portmapper runs is started." -- Mathias </blockquote> </div> -- Party On, Adam