On 15/08/07, James Knott <[EMAIL PROTECTED]> wrote: > > > Perhaps I'm missing something. There's no reason for a user to need > /export/home. A symlink will take care of that too. >
Let's say we have Workstation A and Workstation B and the server. All home directories for all users are hosted on the server under /export/home, which is exported via NFS. All workstations NFS mount the export from the server to a local /export/home mount point. The server is also a LDAP server and all users are added to the LDAP server. Lets' say we have user john. He comes in today and sit in cubicle 1 where workstation A is. He logs in, but Worstation A does not have a local user called john, so it authenticates against the LDAP server, which tells it that the user's home directory is /export/home/john So, john can work on his files from Workstation A, via the NFS mount. Tomorrow John comes in and sit in cubicle 2 at Workstation B, he logs in, and gets his same home directory with his files (which are actually on the server). So, it does not matter which workstation or thin client a user use, they always get their files. Now, if you set up the user in LDAP and make his home directory /home/john, then when he logs into one of the workstations, it will look for his home directory in /home/john on the workstation, but it does not exist and even if it created it there, it is not his real home. Now, if we symlink /home to /export/home on the workstation, then a local user, that only use that workstation and does not make use of the server, will have a home directory on /export/home. And we don't want that. We want to keep static users and roaming users apart -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: [EMAIL PROTECTED] | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
