svn commit: samba-docs r262 - in trunk/Samba-HOWTO-Collection: .

[jht at samba.org]

Author: jht
Date: 2004-10-31 04:29:16 +0000 (Sun, 31 Oct 2004)
New Revision: 262

WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba-docs&rev=262

Log:
Work in progress commit - Adding IDMAP documentation.
Modified:
   trunk/Samba-HOWTO-Collection/IDMAP.xml


Changeset:
Modified: trunk/Samba-HOWTO-Collection/IDMAP.xml
===================================================================
--- trunk/Samba-HOWTO-Collection/IDMAP.xml	2004-10-31 04:16:36 UTC (rev 261)
+++ trunk/Samba-HOWTO-Collection/IDMAP.xml	2004-10-31 04:29:16 UTC (rev 262)
@@ -8,12 +8,16 @@
 
 ]>
 
-<chapter id="groupmapping">
+<chapter id="idmapper">
 <chapterinfo>
 	&author.jht;
 </chapterinfo>
 <title>Identity Mapping &smbmdash; IDMAP</title>
 
+<note><para>
+THIS IS A WORK IN PROGRESS - it is a preparation for the release of Samba-3.0.8.
+</para></note>
+
 <para>
 The Microsoft Windows operating system has a number of features that impose specific challenges
 for interoperability with operaing system on which Samba is implemented. This chapter deals
@@ -56,14 +60,27 @@
 	<title>Stand-Alone Samba Server</title>
 
 	<para>
+	A stand-alone Samba server is an implementation that is not a member of a Windows NT4 Domain,
+	a Windows 200X Active Directory Domain, or of a Samba Domain.
 	</para>
 
+	<para>
+	By definition, this means that users and groups will be created and controlled locally and
+	the identity of a network user must match a local UNIX/Linux user login. The IDMAP facility
+	is therefore of little to no interest, winbind will not be necessary, and the IDMAP facility
+	will not be relevant or of interest.
+	</para>
+
 	</sect2>
 
 	<sect2>
 	<title>Domain Member Server or Domain Member Client</title>
 
 	<para>
+	Samba-3 can act as a Windows NT4 PDC or BDC thereby providing domain control protocols that
+	are based on Windows NT4. Thus, where Samba-3 is a Domain Member server or client the matter
+	if SID to UID/GID resolution is equivalent with the same configuration with a Windows NT4 or
+	earlier domain environment.
 	</para>
 
 	</sect2>