Changeset a4495da for chapter07/udev.xml


Ignore:
Timestamp:
04/17/2005 11:03:59 PM (19 years ago)
Author:
Jim Gifford <jim@…>
Children:
af9b59e
Parents:
a2d4711a
Message:

Text updates from Matt

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/multi-arch/BOOK@4993 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter07/udev.xml

    ra2d4711a ra4495da  
    3131resides entirely in memory and does not take up any disk space).
    3232Device nodes do not require much disk space, so the memory that is
    33 used in negligable.</para>
     33used is negligible.</para>
    3434
    3535<sect2>
     
    153153<title>Handling Hotpluggable/Dynamic Devices</title>
    154154
    155 <para>When you plug in a device, such a Universal Serial Bus (USB) MP3 player, the kernel
     155<para>When you plug in a device, such as a Universal Serial Bus (USB) MP3 player, the kernel
    156156recognizes that the device is now connected and generates a hotplug
    157157event. If the driver is already loaded (either because it was compiled
     
    160160be called upon to create the relevant device node(s) according to the
    161161<systemitem class="filesystem">sysfs</systemitem> data available in
    162 <filename class="directory">/sys</filename>.  If the driver for the
    163 just plugged in device is available as a module but currently unloaded,
    164 then attaching the device to the system will only cause the kernel's
    165 bus driver to generate a hotplug event that notifies userspace of the
    166 new device connection and it not being attached to a driver. In
    167 effect, nothing happens and the device itself is not usable
    168 yet.</para>
    169 
    170 <para>If building a system that has a lot of drivers compiled as
    171 modules rather than directly built into the kernel, using the
    172 <command>S05modules</command> may not be practical. The Hotplug
    173 package (see <ulink url="http://linux-hotplug.sourceforge.net/"/>) can
    174 be beneficial in these cases. When the Hotplug package is installed,
    175 it will respond to the aforementioned kernel's bus driver hotplug
    176 events. The Hotplug package will load the appropriate module and make
    177 this device available by creating the device node(s) for it.</para>
     162<filename class="directory">/sys</filename>.</para>
     163
     164<para>If the driver for the just plugged in device is available as a module but
     165currently unloaded, the Hotplug package will load the appropriate module
     166and make this device available by creating the device node(s) for it.</para>
    178167</sect2>
    179168
Note: See TracChangeset for help on using the changeset viewer.