Very large number of markup fixes, layout updates, etc.

(This used to be commit 8dfbaafb843d17b865855ba1fef1e62cd38d3964)

1 files changed, 94 insertions, 71 deletions

diff --git a/docs/docbook/projdoc/AccessControls.xml b/docs/docbook/projdoc/AccessControls.xml
index 74269616aa..661cc1ca86 100644
--- a/docs/docbook/projdoc/AccessControls.xml
+++ b/docs/docbook/projdoc/AccessControls.xml
@@ -146,10 +146,11 @@ at how Samba helps to bridge the differences.
 	to depths of control ability should review the &smb.conf; man page.
 	</para>
 
-	<itemizedlist>
-	<title>File System Feature Comparison</title>
-		<listitem>
-		<para><emphasis>Name Space</emphasis></para>
+	<variablelist>
+		<title>File System Feature Comparison</title>
+		<varlistentry>
+			<term>Name Space</term>
+			<listitem>
 		<para>
 		MS Windows NT4 / 200x/ XP files names may be up to 254 characters long, Unix file names
 		may be 1023 characters long. In MS Windows file extensions indicate particular file types,
@@ -158,10 +159,12 @@ at how Samba helps to bridge the differences.
 		<para>
 		What MS Windows calls a Folder, Unix calls a directory,
 		</para>
-		</listitem>
+			</listitem>
+		</varlistentry>
 
-		<listitem>
-		<para><emphasis>Case Sensitivity</emphasis></para>
+		<varlistentry>
+			<term>Case Sensitivity</term>
+			<listitem>
 		<para>
 		MS Windows file names are generally Upper Case if made up of 8.3 (ie: 8 character file name
 		and 3 character extension. If longer than 8.3 file names are Case Preserving, and Case
@@ -186,18 +189,22 @@ at how Samba helps to bridge the differences.
 		first will be accessible to MS Windows users, the others are invisible and unaccessible - any
 		other solution would be suicidal.
 		</para>
-		</listitem>
+			</listitem>
+		</varlistentry>
 
-		<listitem>
-		<para><emphasis>Directory Separators</emphasis></para>
+		<varlistentry>
+			<term>Directory Separators</term>
+			<listitem>
 		<para>
 		MS Windows and DOS uses the back-slash '\' as a directory delimiter, Unix uses the forward-slash '/'
 		as it's directory delimiter. This is transparently handled by Samba.
 		</para>
-		</listitem>
+			</listitem>
+		</varlistentry>
 
-		<listitem>
-		<para><emphasis>Drive Identification</emphasis></para>
+		<varlistentry>
+			<term>Drive Identification</term>
+			<listitem>
 		<para>
 		MS Windows products support a notion of drive letters, like <command>C:</command> to represent
 		disk partitions. Unix has NO concept if separate identifiers for file partitions since each
@@ -205,20 +212,24 @@ at how Samba helps to bridge the differences.
 		The Unix directory tree begins at '/', just like the root of a DOS drive is specified like
 		<command>C:\</command>.
 		</para>
-		</listitem>
+			</listitem>
+		</varlistentry>
 
-		<listitem>
-		<para><emphasis>File Naming Conventions</emphasis></para>
+		<varlistentry>
+			<term>File Naming Conventions</term>
+			<listitem>
 		<para>
 		MS Windows generally never experiences file names that begin with a '.', while in Unix these
 		are commonly found in a user's home directory. Files that begin with a '.' are typically
 		either start up files for various Unix applications, or they may be files that contain
 		start-up configuration data.
 		</para>
-		</listitem>
-	
-		<listitem>
-		<para><emphasis>Links and Short-Cuts</emphasis></para>
+			</listitem>
+		</varlistentry>
+
+		<varlistentry>
+			<term>Links and Short-Cuts</term>
+			<listitem>
 		<para>
 		MS Windows make use of "links and Short-Cuts" that are actually special types of files that will
 		redirect an attempt to execute the file to the real location of the file. Unix knows of file and directory
@@ -230,8 +241,9 @@ at how Samba helps to bridge the differences.
 		referred to as 'soft links'. A hard link is something that MS Windows is NOT familiar with. It allows
 		one physical file to be known simulataneously by more than one file name.
 		</para>
-		</listitem>
-	</itemizedlist>
+			</listitem>
+		</varlistentry>
+	</variablelist>
 
 	<para>
 	There are many other subtle differences that may cause the MS Windows administrator some temporary discomfort
@@ -312,7 +324,7 @@ at how Samba helps to bridge the differences.
 	The permissions field is made up of:
 
 	<programlisting>
-	<!-- JRV: Put this into a diagram of some sort -->
+	<comment> JRV: Put this into a diagram of some sort</comment>
 	[ type  ] [ users ] [ group ] [ others ]   [File, Directory Permissions]
 	[ d | l ] [ r w x ] [ r w x ] [ r w x  ]
 	  |   |     | | |     | | |     | | |
@@ -332,13 +344,16 @@ at how Samba helps to bridge the differences.
 
 	<para>
 	Any bit flag may be unset. An unset bit flag is the equivalent of 'Can NOT' and is represented as a '-' character.
-	<!-- FIXME -->
-	<programlisting>
-	<title>Example File</title>
+
+	<example>
+		<title>Example File</title>
+		<programlisting>
 		-rwxr-x---   Means: The owner (user) can read, write, execute
 		                    the group can read and execute
 		                    everyone else can NOT do anything with it
-	</programlisting>
+		</programlisting>
+	</example>
+
 	</para>
 
 	<para>
@@ -346,7 +361,7 @@ at how Samba helps to bridge the differences.
 	</para>
 
 	<para>
-		The letters `rwxXst' set permissions for the user, group and others as: read (r), write (w), execute (or access for directories) (x),r
+	The letters `rwxXst' set permissions for the user, group and others as: read (r), write (w), execute (or access for directories) (x),r
 	execute  only  if  the  file  is a directory or already has execute permission for some user (X), set user or group ID on execution (s),
 	sticky (t).
 	</para>
@@ -365,7 +380,7 @@ at how Samba helps to bridge the differences.
 	</para>
 
 	<para>
-	When a directory is set <command>drw-r-----</command> this means that the owner can read and create (write) files in it, but because
+	When a directory is set <constant>drw-r-----</constant> this means that the owner can read and create (write) files in it, but because
 	the (x) execute flags are not set files can not be listed (seen) in the directory by anyone. The group can read files in the
 	directory but can NOT create new files. NOTE: If files in the directory are set to be readable and writable for the group, then
 	group members will be able to write to (or delete) them.
@@ -388,10 +403,10 @@ Before using any of the following options please refer to the man page for &smb.
 
 	<para>
 	User and group based controls can prove very useful. In some situations it is distinctly desirable to affect all
-	file system operations as if a single user is doing this, the use of the <emphasis>force user</emphasis> and 
-	<emphasis>force group</emphasis> behaviour will achieve this. In other situations it may be necessary to affect a
+	file system operations as if a single user is doing this, the use of the <parameter>force user</parameter> and 
+	<parameter>force group</parameter> behaviour will achieve this. In other situations it may be necessary to affect a
 	paranoia level of control to ensure that only particular authorised persons will be able to access a share or
-	it's contents, here the use of the <emphasis>valid users</emphasis> or the <emphasis>invalid users</emphasis> may
+	it's contents, here the use of the <parameter>valid users</parameter> or the <parameter>invalid users</parameter> may
 	be most useful.
 	</para>
 
@@ -665,7 +680,7 @@ Before using any of the following options please refer to the man page for &smb.
 	By default samba sets no restrictions on the share itself. Restrictions on the share itself
 	can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can
 	connect to a share. In the absence of specific restrictions the default setting is to allow
-	the global user <emphasis>Everyone</emphasis> Full Control (ie: Full control, Change and Read).
+	the global user <constant>Everyone</constant> Full Control (ie: Full control, Change and Read).
 	</para>
 
 	<para>
@@ -701,13 +716,13 @@ Before using any of the following options please refer to the man page for &smb.
 			<procedure>
 			<title>Instructions</title>
 			<step><para>
-			Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu
-			select Computer, then click on the Shared Directories entry.
+			Launch the <application>NT4 Server Manager</application>, click on the Samba server you want to administer, then from the menu
+			select <guimenu>Computer</guimenu>, then click on the <guimenuitem>Shared Directories</guimenuitem> entry.
 			</para></step>
 
 			<step><para>
-				Now click on the share that you wish to manage, then click on the Properties tab, next click on
-				the Permissions tab. Now you can Add or change access control settings as you wish.
+			Now click on the share that you wish to manage, then click on the <guilabel>Properties</guilabel> tab, next click on
+			the <guilabel>Permissions</guilabel> tab. Now you can add or change access control settings as you wish.
 			</para></step>
 			</procedure>
 
@@ -717,14 +732,14 @@ Before using any of the following options please refer to the man page for &smb.
 			<title>Windows 200x/XP</title>
 
 			<para>
-			On MS Windows NT4/200x/XP system access control lists on the share itself are set using native
+			On <application>MS Windows NT4/200x/XP</application> system access control lists on the share itself are set using native
 			tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder,
-			then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows
-			<emphasis>Everyone</emphasis> Full Control on the Share.
+			then select <guimenuitem>Sharing</guimenuitem>, then click on <guilabel>Permissions</guilabel>. The default 
+			Windows NT4/200x permission allows <emphasis>Everyone</emphasis> Full Control on the Share.
 			</para>
 
 			<para>
-			MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the
+			MS Windows 200x and later all comes with a tool called the <application>Computer Management</application> snap-in for the
 			Microsoft Management Console (MMC). This tool is located by clicking on <filename>Control Panel ->
 			Administrative Tools -> Computer Management</filename>.
 			</para>
@@ -732,21 +747,22 @@ Before using any of the following options please refer to the man page for &smb.
 			<procedure>
 			<title>Instructions</title>
 			<step><para>
-				After launching the MMC with the Computer Management snap-in, click on the menu item 'Action',
-				select 'Connect to another computer'. If you are not logged onto a domain you will be prompted
+				After launching the MMC with the Computer Management snap-in, click on the menu item <guimenuitem>Action</guimenuitem>,
+				select <guilabel>Connect to another computer</guilabel>. If you are not logged onto a domain you will be prompted
 				to enter a domain login user identifier and a password. This will authenticate you to the domain.
 				If you where already logged in with administrative privilidge this step is not offered.
 			</para></step>
 
 			<step><para>
-			If the Samba server is not shown in the Select Computer box, then type in the name of the target
-			Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+]
-			next to 'Shared Folders' in the left panel.
+			If the Samba server is not shown in the <guilabel>Select Computer</guilabel> box, then type in the name of the target
+			Samba server in the field <guilabel>Name:</guilabel>. Now click on the <guibutton>[+]</guibutton> next to 
+			<guilabel>System Tools</guilabel>, then on the <guibutton>[+]</guibutton> next to <guilabel>Shared Folders</guilabel> in the 
+			left panel.
 			</para></step>
 
 			<step><para>
 			Now in the right panel, double-click on the share you wish to set access control permissions on.
-			Then click on the tab 'Share Permissions'. It is now possible to add access control entities
+			Then click on the tab <guilabel>Share Permissions</guilabel>. It is now possible to add access control entities
 			to the shared folder. Do NOT forget to set what type of access (full control, change, read) you
 			wish to assign for each entry.
 			</para></step>
@@ -754,10 +770,10 @@ Before using any of the following options please refer to the man page for &smb.
 
 			<warning>
 			<para>
-			Be careful. If you take away all permissions from the Everyone user without removing this user
+			Be careful. If you take away all permissions from the <constant>Everyone</constant> user without removing this user
 			then effectively no user will be able to access the share. This is a result of what is known as
-			ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone
-			will have no access even if this user is given explicit full control access.
+			ACL precidence. ie: Everyone with <strong>no access</strong> means that MaryK who is part of the group 
+			<constant>Everyone</constant> will have no access even if this user is given explicit full control access.
 			</para>
 			</warning>
 
@@ -798,19 +814,19 @@ Before using any of the following options please refer to the man page for &smb.
 		<para>From an NT4/2000/XP client, single-click with the right 
 		mouse button on any file or directory in a Samba mounted 
 		drive letter or UNC path. When the menu pops-up, click 
-		on the <emphasis>Properties</emphasis> entry at the bottom of 
+		on the <guilabel>Properties</guilabel> entry at the bottom of 
 		the menu. This brings up the file properties dialog
-		box. Click on the tab <emphasis>Security</emphasis> and you 
-		will see three buttons, <emphasis>Permissions</emphasis>,	 
-		<emphasis>Auditing</emphasis>, and <emphasis>Ownership</emphasis>. 
-		The <emphasis>Auditing</emphasis> button will cause either 
+		box. Click on the tab <guilabel>Security</guilabel> and you 
+		will see three buttons, <guibutton>Permissions</guibutton>,	 
+		<guibutton>Auditing</guibutton>, and <guibutton>Ownership</guibutton>. 
+		The <guibutton>Auditing</guibutton> button will cause either 
 		an error message <errorname>A requested privilege is not held 
 		by the client</errorname> to appear if the user is not the 
 		NT Administrator, or a dialog which is intended to allow an 
 		Administrator to add auditing requirements to a file if the 
 		user is logged on as the NT Administrator. This dialog is 
 		non-functional with a Samba share at this time, as the only 
-		useful button, the <command>Add</command> button will not currently 
+		useful button, the <guibutton>Add</guibutton> button will not currently 
 		allow a list of users to be seen.</para>
 
 	</sect2>
@@ -849,8 +865,8 @@ Before using any of the following options please refer to the man page for &smb.
 		and allow a user with Administrator privilege connected 
 		to a Samba server as root to change the ownership of 
 		files on both a local NTFS filesystem or remote mounted NTFS 
-		or Samba drive. This is available as part of the <emphasis>Seclib
-		</emphasis> NT security library written by Jeremy Allison of 
+		or Samba drive. This is available as part of the <application>Seclib
+		</application> NT security library written by Jeremy Allison of 
 		the Samba Team, available from the main Samba ftp site.</para>
 
 	</sect2>
@@ -921,7 +937,7 @@ Before using any of the following options please refer to the man page for &smb.
 			<para>Directories on an NT NTFS file system have two 
 			different sets of permissions. The first set of permissions 
 			is the ACL set on the directory itself, this is usually displayed 
-			in the first set of parentheses in the normal <command>"RW"</command> 
+			in the first set of parentheses in the normal <constant>"RW"</constant> 
 			NT style. This first set of permissions is created by Samba in 
 			exactly the same way as normal file permissions are, described 
 			above, and is displayed in the same way.</para>
@@ -995,12 +1011,16 @@ Before using any of the following options please refer to the man page for &smb.
 
 		<para>There are four parameters 
 		to control interaction with the standard Samba create mask parameters.
-		These are :</para>
+		These are :
+
+		<simplelist>
+			<member><parameter>security mask</parameter></member>
+			<member><parameter>force security mode</parameter></member>
+			<member><parameter>directory security mask</parameter></member>
+			<member><parameter>force directory security mode</parameter></member>
+		</simplelist>
 
-		<para><parameter>security mask</parameter></para>
-		<para><parameter>force security mode</parameter></para>
-		<para><parameter>directory security mask</parameter></para>
-		<para><parameter>force directory security mode</parameter></para>
+		</para>
 
 		<para>Once a user clicks <guibutton>OK</guibutton> to apply the 
 		permissions Samba maps the given permissions into a user/group/world 
@@ -1061,12 +1081,15 @@ Before using any of the following options please refer to the man page for &smb.
 		<para>If you want to set up a share that allows users full control
 		in modifying the permission bits on their files and directories and
 		doesn't force any particular bits to be set 'on', then set the following
-		parameters in the &smb.conf; file in that share specific section :</para>
+		parameters in the &smb.conf; file in that share specific section :
+		</para>
 
-		<para><parameter>security mask = 0777</parameter></para>
-		<para><parameter>force security mode = 0</parameter></para>
-		<para><parameter>directory security mask = 0777</parameter></para>
-		<para><parameter>force directory security mode = 0</parameter></para>
+		<simplelist>
+			<member><parameter>security mask = 0777</parameter></member>
+			<member><parameter>force security mode = 0</parameter></member>
+			<member><parameter>directory security mask = 0777</parameter></member>
+			<member><parameter>force directory security mode = 0</parameter></member>
+		</simplelist>
 	</sect2>
 
 	<sect2>
@@ -1193,7 +1216,7 @@ are examples taken from the mailing list in recent times.
 		</para>
 
 		<para>
-		You should see that the file 'Afile' created by Jill will have ownership
+		You should see that the file <filename>Afile</filename> created by Jill will have ownership
 		and permissions of Jack, as follows:
 		<screen>
 		-rw-r--r--  1 jack  engr     0 2003-02-04 09:57 Afile
@@ -1211,7 +1234,7 @@ are examples taken from the mailing list in recent times.
 		</para>
 
 		<note><para>
-		The above are only needed IF your users are NOT members of the group
+		The above are only needed <strong>if</strong> your users are <strong>not</strong> members of the group
 		you have used. ie: Within the OS do not have write permission on the directory.
 		</para>
 		</note>