* Reword handling of hotpluggable devices now that we install the hotplug package

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4978 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Matthew Burgess 2005-04-16 16:06:59 +00:00
parent 1e4802278c
commit 06e7f6e35b
2 changed files with 7 additions and 15 deletions

View File

@ -83,6 +83,9 @@ first a summary, then a detailed log.</para>
</itemizedlist> </itemizedlist>
</listitem> </listitem>
<listitem><para>April 16, 2005 [matt]: Reword handling of hotpluggable devices
now that we install the hotplug package (Andrew Benton)</para></listitem>
<listitem><para>April 16, 2005 [matt]: Minor wording/typo fixes (Allard Welter) <listitem><para>April 16, 2005 [matt]: Minor wording/typo fixes (Allard Welter)
</para></listitem> </para></listitem>

View File

@ -154,22 +154,11 @@ into the kernel or because it was loaded via the
<command>S05modules</command> bootscript), <command>udev</command> will <command>S05modules</command> bootscript), <command>udev</command> will
be called upon to create the relevant device node(s) according to the be called upon to create the relevant device node(s) according to the
<systemitem class="filesystem">sysfs</systemitem> data available in <systemitem class="filesystem">sysfs</systemitem> data available in
<filename class="directory">/sys</filename>. If the driver for the <filename class="directory">/sys</filename>.</para>
just plugged in device is available as a module but currently unloaded,
then attaching the device to the system will only cause the kernel's
bus driver to generate a hotplug event that notifies userspace of the
new device connection and it not being attached to a driver. In
effect, nothing happens and the device itself is not usable
yet.</para>
<para>If building a system that has a lot of drivers compiled as <para>If the driver for the just plugged in device is available as a module but
modules rather than directly built into the kernel, using the currently unloaded, the Hotplug package will load the appropriate module
<command>S05modules</command> may not be practical. The Hotplug and make this device available by creating the device node(s) for it.</para>
package (see <ulink url="http://linux-hotplug.sourceforge.net/"/>) can
be beneficial in these cases. When the Hotplug package is installed,
it will respond to the aforementioned kernel's bus driver hotplug
events. The Hotplug package will load the appropriate module and make
this device available by creating the device node(s) for it.</para>
</sect2> </sect2>
<sect2> <sect2>