That's a good idea, and probably the one that will end up being the least conflict prone.
What exactly do you mean by "universal nfs mount"? I'm not familiar with the term and I can't find any reference online to it.
Ya, and I know at least on Linux you can use a mount option to set the default GID and permissions for newly created files and directories.
gid=7777,umask=003
or this to only allow the user and group members to be able to even read the files.
gid=7777,umask=007
Owe well, I just thought that term seemed to fit.
]]>What exactly do you mean by "universal nfs mount"? I'm not familiar with the term and I can't find any reference online to it.
]]>That would be the easy way to go, but may not work depending on what you want to put in a universal nfs mount.
]]>I've seen the proposed list of standard uid and gid numbers in the Arch wiki. I'm trying to decide which groups to change in order to create the least amount of havoc. For example, right now the generic users group in Arch has a gid of 100. On OpenBSD that gid is reserved for _ldapd, the OpenBSD ldap daemon.
Will I create more havoc by trying to change the major distro default linux users gid of 100 to something else? I want to use the OpenBSD ldap daemon too, so will changing the gid of that make life difficult in that respect?
If someone has experience with standardizing uids and gids across a network of heterogeneous unixy systems, please weigh in.
]]>