- https://en.wikipedia.org/wiki/Network_File_System = NFS
- https://en.wikipedia.org/wiki/Network_Information_Service = NIS
- https://en.wikipedia.org/wiki/Andrew_File_System = AFS (Mac OS X)
- https://en.wikipedia.org/wiki/CIFS AKA SMB AKA Samba
- https://en.wikipedia.org/wiki/Unix_security#Root_squash – re “root=…”
- http://linux.die.net/man/5/exports – /etc/exports
My (reduced) I.T. landscape:
- a Synology DiskStation NAS (with some Linux and “Busybox”) functions as an NFS server
- an openSUSE Linux VM is the relevant NFS client – the other clients don’t use NFS but AFS (for the Macs) and Samba (…)
True, I am not using NIS.
True, my server and my client don’t have the same values for corresponding users (UIDs). Should I better “chown -R …” the respective users’ directory trees on the NAS in order to achieve the proper UID mapping?!?
My NFS server does not accept “root=…”.
Is making brute force use of “anonuid=…” on the server side (mapping all accesses from outside to a single user w/o further proper authentication) the only (and admittedly unappropriate) way to achieve my goal then? Yes, I do have an idea of what anonuid should be used for.
AFS and Samba seem to be able to deal with user accounts, that do not have the same UIDs on both sides – how to deal with that in the NFS context w/o NIS?!?
Update 2015-01-26: Simply use the relevant NAS users’ UIDs also on the NFS clients. Get rid of all explicit UID squashing and mapping.