On the Linux side it was very simple, I used the Webmin Server configurator that comes with Redhat. I simply exported the volumes to my IP address and added myself as a read/write user. I tested it with this command:
% sudo mount server:/path/to/export /home/username/server/This worked fine, but was only temporary. It needed to be performed at every boot.
[Editor's note: The following information deals with modifying the NetInfo database. Proceed at your own risk, and make sure you know what you're doing -- I have not tested this hint myself!]
Next I looked at Netinfo on an OS X 1.2 server, which I installed onto a 9600/200. It is not very user freindly, but it does have buttons for easily adding NFS mounts to netinfo. I used that to get the basic Netinfo settings I would need. This machine is invaluable for hacking Netinfo on OS X 10.1.x or 10.2.
In Netinfo, add a new Directory at the root level named "mounts". You need a new directory inside of mounts for each mountpoint. You will need three new properties inside of these directories. The first is "name", and it has a value that is the same as the path to the NFS export you want to mount. The next is "dir", and it has a value that is the same as the directory path to where you want to mount it locally. Now we need a "type" property. This lets OS X know what kind of filesystem to mount. In this case it is "nfs". So the final settings look like this:
- name: 192.168.10.10/home/username
- dir: /Users/yourname/mount
- type: nfs
Now to the fun part. If you reboot, your mounts should work, but then you are locked in to a directory or path until you reboot again. I hate to reboot my machine, so i looked for a solution.Here it is:
% sudo kill -1 `cat/var/run/automount.pid`This kills and restarts the automount process. This is also useful if you decide you want to change the icon on your automount directory. You must do it before the system takes hold of it. Plus if you want to add more mounts it is simple, and makes experimenting with the placement of the directories less of a chore.
This method of mounting is better than adding the NFS mounts to fstab, because they are dynamic instead of static. This means that they are only called on by the system when a user or process tries to access them. Static mounts can cause the system to hang at startup if the server is not available. Dynamic mounts do not. This makes them excellent for use on laptops as well, since you may not always have access to the sever when you boot.

