Index: introduction/welcome/changelog.xml
===================================================================
--- introduction/welcome/changelog.xml	(revision 1fc9e7ed2065533bf2d82224e384293b33351458)
+++ introduction/welcome/changelog.xml	(revision 44a3b4f088e0385622be774dc29d01ff69a727f6)
@@ -11,4 +11,7 @@
 
 <itemizedlist>
+
+<listitem><para>October 21st, 2003 [larry]: OpenLDAP: expanded configure
+section to the point of personalization.</para></listitem>
 
 <listitem><para>October 21st, 2003 [igor]: Fixed MPlayer subtitle font
Index: postlfs/config/bootdisk.xml
===================================================================
--- postlfs/config/bootdisk.xml	(revision 1fc9e7ed2065533bf2d82224e384293b33351458)
+++ postlfs/config/bootdisk.xml	(revision 44a3b4f088e0385622be774dc29d01ff69a727f6)
@@ -60,4 +60,12 @@
 <para>These instructions presume a base <acronym>LFS</acronym> install
 using ext2/ext3 file systems.</para>
+
+<para>The kernel versions 2.4.22 and 2.6 before test6 have a deficiency
+that prevents busybox and similar applications from booting correctly.
+You need to download and apply the
+<ulink url="&patch-root;/linux-2.4.22-init-1.patch">init-1</ulink>
+patch that corrects this, letting busybox be used for our
+application, and rebuild your kernel. Take care of the below kernel
+items while you are at it.</para>
 
 <para>You need to have loopback device support enabled in your host's
Index: server/other/openldap/openldap-config.xml
===================================================================
--- server/other/openldap/openldap-config.xml	(revision 1fc9e7ed2065533bf2d82224e384293b33351458)
+++ server/other/openldap/openldap-config.xml	(revision 44a3b4f088e0385622be774dc29d01ff69a727f6)
@@ -12,10 +12,44 @@
 to run <command>ldconfig</command>. The <acronym>LDAP</acronym> server
 can be started by <command>/usr/sbin/slapd</command> as described in 
-the man page slapd(8).</para>
+the man page slapd(8). You can verify that <acronym>LDAP</acronym> is
+running with <command>ps aux</command> and you can verify access to the
+<acronym>LDAP</acronym> server with the following command:</para>
+<screen><userinput><command>ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts</command></userinput></screen>
+
+<para>The correct result is:</para>
+<screen><computeroutput># extended LDIF
+#
+# LDAPv3
+# base <> with scope base
+# filter: (objectclass=*)
+# requesting: namingContexts 
+#
+
+#
+dn:
+namingContexts: dc=my-domain,dc=com
+
+# search result
+search: 2
+result: 0 Success
+
+# numResponses: 2
+# numEntries: 1</computeroutput></screen>
+
+<para>Kill the server with this command:</para>
+<screen><userinput><command>kill -INT `cat /var/lib/slapd.pid`</command></userinput></screen>
+
+<para>You are now ready to modify the 
+<filename>/etc/openldap/slapd.conf</filename> to be specific to your
+installation.</para>
+
+<para><emphasis>Utilizing <application>GDBM</application></emphasis></para>
 
 <para>To utilize <application>GDBM</application> as the database
-backend, the "database" entry in <filename>/etc/slapd.conf</filename>
+backend, the "database" entry in <filename>/etc/openldap/slapd.conf</filename>
 must be changed from "bdb" to "ldbm".  You can use both by creating an
-additional database section in <filename>/etc/slapd.conf</filename>.</para>
+additional database section in <filename>/etc/openldap/slapd.conf</filename>.</para>
+
+<para><emphasis>Securing your <acronym>LDAP</acronym> server</emphasis></para>
 
 <para>Significant configuration is needed for
@@ -23,5 +57,8 @@
 security features.  The <ulink
 url="http://www.openldap.org/doc/admin21/">OpenLDAP 2.1 Administrator's
-Guide</ulink> is a good place to start.</para>
+Guide</ulink> is a good place to start for access control settings,
+running as a user other than root and setting a chroot environment.</para>
+
+<para><emphasis>User Tools</emphasis></para>
 
 <para>Data can be added to the <acronym>LDAP</acronym> database via
@@ -29,4 +66,13 @@
 the database. For more information see the appropriate man page.</para>
 
+<para><emphasis><application>Mozilla</application> Address Directory</emphasis></para>
+
+<para>By default, LDAPv2 support is disabled in the
+<filename>slapd.conf</filename> file. Once the database is properly
+setup and <application>Mozilla</application> is configured to use the
+directory, you must add <option>allow bind_v2</option> to the
+<filename>slapd.conf</filename> file.</para>
+
+
 </sect3>
 
