Don't list the initscript in the contents of the Hotplug package

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3687 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

chapter01/changelog.xml

@@ -102,6 +102,10 @@ first a summary, then a detailed log.</para>
 </itemizedlist>
 </listitem>
 
+<listitem><para>May 23th, 2004 [alexander]: Don't list the initscript in the
+contents of the Hotplug package. The reason is that we use winkie's
+replacement script from LFS-Bootscripts.</para></listitem>
+
 <listitem><para>May 23th, 2004 [alexander]: Fixed XML validation
 error.</para></listitem>
 

chapter06/hotplug.xml

@@ -28,7 +28,8 @@ modules into the running kernel.
 <title>Installation of Hotplug</title>
 
 <para>
-Apply the patch that avoids bogus dependencies of the hotplug initscript
+Apply the patch that avoids bogus dependencies of the
+<filename>usb.rc</filename> script
 upon <application>which</application> and
 <application>usbutils</application> packages:
 </para>
@@ -98,23 +99,15 @@ changes in its internal state (e.g. a new device is added or removed).</para>
 </listitem>
 </varlistentry>
 
-<varlistentry>
-<term id="hotplug-initscript"><command>hotplug</command> initscript</term>
-<listitem>
-<indexterm zone="ch-system-hotplug hotplug-initscript"><primary
-sortas="d-hotplug-initscript">hotplug</primary></indexterm>
-<para>This script just runs all
-<filename>/etc/hotplug/*.rc</filename> scripts in turn during system
-startup.</para>
-</listitem>
-</varlistentry>
-
 <varlistentry>
 <term id="hotplug-rc"><command>*.rc</command> files in
 <filename class="directory">/etc/hotplug</filename> directory</term>
 <listitem>
 <para>These scripts are used for cold plugging, i.e. detection and other
-specific actions upon hardware already present during system startup. These
+specific actions upon hardware already present during system startup. 
+They are called by the <filename>hotplug</filename> initscript that comes
+from the lfs-bootscripts package.
+The <command>*.rc</command>
 scripts try to find kernel modules corresponding to your hardware and insert
 them into the running kernel.
 </para>