Joe Sloan wrote:
James Knott wrote:
Aaron Kulkis wrote:
primm wrote:
What NFS allows is the user id number, not name. This means is if user
A is 1000 on one system. Another user 1000 on another system will have
access to A's files. The key is make sure user ID's are consistent
across all systems. Someone with root access could of course create a
new user with whatever ID they want or use an existing ID.
I setup the nfs server with yast. I setup the nfs clients with Yast.
Yast tells me nothing about id. It doen't say, 'are you sure you want
to continue becaus this is s big security risk'.
I come back to my original worry: I'm the only one with root access
on any box on my network. Yast set it up for me. What are my
problems? I'm sorry to have to ask for confirmation.
Just make sure that each user on your network has a UNIQUE
user ID number ... if Joe has user ID 1002 on one machine,
and Jane has user ID 1002 on another machine, then you will
have problems.
You want Joe to have the same user ID (say 1002) on every
machine, and Jane to have her own user ID (say 1003) on
every machine.
The easiest way to do this is with NIS.
With the Windows Domain Login, one option is to create a home
directory. Is this possible with NIS? If not what does one use for a
home directory, when logged onto a computer without a home directory for
that user?
Sure, use the make_home_dir utility - works like a charm.
http://www.trustsec.de/soft/oss/make_home_dir-1.0.tar.gz
Of course, the old school linux method is to combine nis with nfs and
automounter, so you get the same home directory everywhere. But for
limited environments, make_home_dir will fit the bill.
And then the NIS map of the automount files can be used
to allow ANY workstation to automount the home directory
located on the user's "usual" workstation.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
