FreeOS.com: Centralised authentication using NISDec 03, 2000, 17:07 (0 Talkback[s])
(Other stories by Mayank Sarup)
[ Thanks to Mayank for this link. ]
"If users on your network are working on more than one machine you will need to create a login/password pair for them on each machine. A more elegant solution is to maintain a centralized database that client machines refer to for authentication. NIS is one way to do that and this article shows you how."
"To log on to a machine on your network, you need a login/password pair that is valid on that machine. This can become a problem over a larger network where you may have people using more than one machine. An example of this would be your computer lab where people are going to be working off different machines most of the time. You will then be forced to create logins for each user on every machine that they're likely to use. NIS steps in here and provides you with centralized authentication. All the logins are created on a single machine, which client machines access to authenticate users."
"Once you have centralized your authentication, you will also need to make the home directory of the user available to him on the machine that they log on to. If they still have to login to another machine to access their data then it's not very useful having NIS around. NFS or the Network File System allows you to 'export' a directory for mounting on other machines. When mounted, that directory will appear as a local directory on the client machine. This is completely transparent to the user. You can then transfer files, run programs off a NFS mounted directory with great ease."