Changeset 24a08b9 for chapter07

Timestamp:

08/17/2004 10:12:01 PM (20 years ago)

Author:

Gerard Beekmans <gerard@…>

Branches:

6.0

Children:

fa2f5ad

Parents:

6850316

Message:

General edits. Added bash+readline display_wrap patches

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/testing/BOOK@4040 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter07/udev.xml (modified) (1 diff)

chapter07/udev.xml

@@ -153 +153 @@
 <para>When you plug in a device, e.g. a USB MP3 player, the kernel
 recognizes that the device is now connected and generates a hotplug
-event. The driver will already have been loaded (either because it was
-compiled into the kernel, or it was loaded via the
-<command>S05modules</command> bootscript) so <command>udev</command>
-will simply be called upon to create the relevant device node
-according to the <systemitem class="filesystem">sysfs</systemitem>
-data available in <filename class="directory">/sys</filename>.</para>
+event. If the driver is already loaded (either because it was compiled
+into the kernel, or it was loaded via the
+<command>S05modules</command> bootscript) <command>udev</command> will
+be called upon to create the relevant device node(s) according to the
+<systemitem class="filesystem">sysfs</systemitem> data available in
+<filename class="directory">/sys</filename>.  If the driver for the
+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 you are building a system that has a lot of drivers compiled
+as modules rather than directly built into the kernel and using the
+<command>S05modules</command> is not practical then the Hotplug
+package (see <ulink url="http://linux-hotplug.sourceforge.net/"/>) can
+be beneficial. 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>