######################################################################### For the apple notes.....I think. NFS mounting made easy from a Mac OS X box. (Thanks apple, for not really documenting any of this, and when you did you should have just said, "Just kidding!" or by the way, FQDN are not understood here.) Two ways to do this. First: From the "connect to server" GUI, at the bottom where it says "address" enter, nfs://remotefileservername/path/to/shared/folder NOTE: the remotefileservername CANNOT be a fully qualified domain name also, this GUI will want to connect to an unpriveliged port(above 1024), some unices(linux) may have a hard time with this.(one possible fix is to run the file server with the "insecure" option in the /etc/exports file.) Also, if you are using the "no_rootsqaush" option on the exporting host, that the user exist on the exporting host that you are trying to mount as. Otherwise remove the no_rootsquash option and allow the user to come in as anonymous. example: User, bobo, must exist on exporting host if you are trying to NFS mount something there that is being exported with no_rootsquash option. Oh! but wait. There's more to this. Sometimes this doesn't work. Why you ask? When I find out...you'll find out. Another well documented, backwards compatitble, standard followed. Thanks apple, whats next? chicken bones and full moons. What the #@$% is an error -36. Is that the secret? Well it appears the secret is that OS X can't NFS mount a filesystem that is exported using no_rootsquash option. Security reasons? I'm willing to give apple the benefit of the doubt and say, yes , of course it's for security. So, so much for usr bobo. He will become user anonymous anyway and we'll have to depend on directory permissions. Second: You can use the mount_nfs command from the command line with the -P option. This option is said to be ignored in the man page but come on, who would really read the man page. The -P option specifies to use a priveldged port, solving the problem with unix/linux file servers that don't do insecure ports. The syntax looks like; mount_nfs -P remotehost:/path/directory /MacMntPoint Believe it or not they actually use a simple umount to unmount the directory ..........and it just that simple. NFS mounting a linux file server from a Mac OS X workstation: Snippet from linux file server /var/log/messages snip........... Apr 10 11:21:11 pingy kernel: nfsd: request from insecure port (c0a80104:51103)! ..........snip After getting the above message on a linux file server when trying make a nfs mount from a Mac OS X host. I found this on a user groups mailing list This is from the user group.......................................... ....That works if you have only trusted users on your network, but it's not a good idea otherwise. Another method is to use mount_nfs -P server:/dir /localdir which forces the request to come from a privileged port. The man page for mount_nfs says the -P is only for compatibility and is ignored because the request always comes from a privileged port anyway, but the man page lies. ............................................................................ The above would be good to use from a Mac manually mounting a linux box but if you make the following changes to the linux box, voila ! this also from a mailing list................. Assuming you are successfully exporting to other operating systems (implying your NFS server is really 'up' properly), the short answer is possibly: 1) Make sure you have the 'insecure' option specified in the linux server's /etc/exports file, eg. if the mac is 192.168.0.8: /net 192.168.0.8(rw,no_root_squash,insecure) 2) Run 'exportfs -av' on the linux machine after making the modification. 3) Retry the mount from the mac. My real world entry in /etc/exports looks like this: /net 192.168.0.0/255.255.255.248(rw,no_root_squash) 192.168.0.8(rw,no_root_squash,insecure) ..which shows my normal subnet's export options, followed by the special 'insecure' export option for only the mac. In my case, I have a redhat 6.1 linux file server and an imac running OS X.0.4. When I had the problem, I went directly to the linux machine's /var/log/messages to see what errors were being logged about the connections from the mac. What I saw was: ----- Nov 19 23:13:42 tahoe rpc.mountd: authenticated mount request from 192.168.0.8:850 for /net (/net) Nov 19 23:13:42 tahoe kernel: nfsd: request from insecure port (c0a80008:49302)! ----- ..which led me to the above solution. The rule of the sysadmin: if something is wrong, check the logs first ;) Hope that helps. .............................................................................. Other mount protocols available to the "connect to server " GUI. smb://FQDN.are.OK.here afp://FQDN.are.OK.here nfs://NO_FQDN_HERE/path/to/export There may be more who knows and there probably are.