On the (Solaris/OpenSolaris) NFS server, nothing should have to be done any different than for any other NFS client.
Using the same UIDs (and GIDs too) is indeed important, except perhaps with NFSv4, which IMO isn't ready for prime time yet in Leopard. On the Mac side, in my experience, Finder does not play nicely with indirect autofs mounts (like auto_home, for example). Direct mounts work better; I moved my ~/Music/iTunes tree to my Sun and added a direct autofs mount for that (set up an auto_direct map, since I thought the "-static" mounts via special fstab entries were cheesy), and as long as I don't have an iPod plugged in when I log in, that seems to work ok. (Some Mac OS X processes, Finder being one and perhaps ituneshelper or some such being another, don't work right unless the automount has already been triggered.) Maybe I'll just replace that with a mount directly in fstab, that does not involve automounter at all; since the number of user accounts on my Mac is very small, that's not a scalability issue for me. That way, the NFS mount would always be there, and I shouldn't have a problem at all. Over NFS, Mac non-data forks seem to be represented as AppleDouble (or something similar), that is, with an extra file whose name is prefixed with "._". I doubt that ACLs work, although maybe once NFSv4 is sensible, maybe they would then. As with anything, best to avoid "soft" mounts and use "intr" instead. Both Solaris and the Mac have enough documentation to figure all the rest out, if you can find it. :-) (and no, I didn't take notes or remember _where_, so please do your own research) Macs _do_ have man pages, although you have to either use Terminal or scrounge a GUI man page viewer to see them. I've also gotten SMB mounts to work against the OpenSolaris smbd server (not Samba). I think that required adding the following pam.conf entries (after all others with the same first column): login auth optional pam_smbfs_login.so.1 other password required pam_smb_passwd.so.1 And then I think I had to change the password for my account, and maybe do something with smbadm(1m); I forget... And of course enable the service svc:/network/smb/server:default Thus far, I've had less luck getting Samba (from blastwave) on a Solaris 9 box working with the Mac...but I wasn't really interested enough to keep at it, since NFS was doing mostly well enough for me. -- This message posted from opensolaris.org