active directory under *nix
Hello,
I have two questions to ask:
1) Windows2000 has "active directory" as one of its greatest features. Does it have a counterpart under UNIX/Linux systems? if not, what does a *NIX system use?
2) i found the windows way of assigning permissions confusing. under *nix, there are only 3 attributes: read, write and execute. but under windows2000, we have: read, write, read and execute, modify and full control! is there an easy way to memorizing these two permission systems?
Thanks,
KEN
I have two questions to ask:
1) Windows2000 has "active directory" as one of its greatest features. Does it have a counterpart under UNIX/Linux systems? if not, what does a *NIX system use?
2) i found the windows way of assigning permissions confusing. under *nix, there are only 3 attributes: read, write and execute. but under windows2000, we have: read, write, read and execute, modify and full control! is there an easy way to memorizing these two permission systems?
Thanks,
KEN
ASKER
hi,
1) well, by "memorizing", i mean memorizing similarities/differences and keep them in my brain. :)
"each has its advantages and disadvantages"? but i found it's easier to understand and follow the *nix way. can you tell me the disadvantages of the *nix way of setting permissions?
2) just a quick question:
under windows2000 there's "scheduled tasks" but it still needs your login and password when the scheduled time comes---someone told me it's for "better security purposes". is it the case that under *nix, you don't have to do that? i mean, suppose you want the system to back up everything on every Sunday at 3pm, do you just do some shell scripting and let the system do its job when the scheduled time comes, or do you still have to, like that on windows system, be physically on the spot on every Sunday at 3pm and key in your login name and password? if the answer for the above question is "no", Why can't windows just let the system do what it's supposed to do without authentication?
Thanks,
KEN
1) well, by "memorizing", i mean memorizing similarities/differences and keep them in my brain. :)
"each has its advantages and disadvantages"? but i found it's easier to understand and follow the *nix way. can you tell me the disadvantages of the *nix way of setting permissions?
2) just a quick question:
under windows2000 there's "scheduled tasks" but it still needs your login and password when the scheduled time comes---someone told me it's for "better security purposes". is it the case that under *nix, you don't have to do that? i mean, suppose you want the system to back up everything on every Sunday at 3pm, do you just do some shell scripting and let the system do its job when the scheduled time comes, or do you still have to, like that on windows system, be physically on the spot on every Sunday at 3pm and key in your login name and password? if the answer for the above question is "no", Why can't windows just let the system do what it's supposed to do without authentication?
Thanks,
KEN
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
2) don't know what you mean by "memorize" (please explain), but the answer is: NO
both techniques are distingued, can be compared somehow, each has its advantags and disadvantages
*nix have a add-on called ACL (user access lists), which is more powerfull, IMHO, but in rare use