There are numerous operational questions that this raises. I'll mention one of them. Suppose that the NIS server resides on a UNIX host and that NIS maps are maintained for users there. In that case, it's necessary to modify Active Directory to add a user in addition to modifying the NIS maps on the UNIX NIS server. Now suppose one were to use the SFU server for NIS, which would reside on a Windows 2000 domain controller. Would the need to define users twice go away? Would it be sufficient to modify Active Directory to add a user, which would then be added to the NIS maps maintained in server for NIS? This is a serious operational issue: one wants to avoid having to define users in two parallel databases: active directory and NIS. F. Lengyel -----Original Message----- From: Craig Spurgeon [mailto:craigs@quiknet.com] Sent: Tuesday, December 18, 2001 11:11 AM To: pam-list@redhat.com Subject: Re: Active Directory module? Microsoft realized that many sites would have a heterogeneous mix of Windows and Unix servers. The Services For Unix package contains a feature called NIS which includes the LDAP Posix schema. This schema defines interoperability parameters for Windows and Unix, such as UID, GID, home directory, default shell etc. Active Directory will use the Posix schema if installed. Thus you get UIDs and GIDs that cause no conflicts between Windows and Unix, Linux, and other flavors. -- Craig C Spurgeon linuxguru@quiknet.com I set about one day to make a list of the innovations that are attributable to Microsoft. Once I realized that Ctrl-Alt-Del was handled in the BIOS, it turned out that there aren't any. _______________________________________________ Pam-list@redhat.com https://listman.redhat.com/mailman/listinfo/pam-list
