Changeset 01fd09f
- Timestamp:
- 04/16/2005 04:09:09 PM (19 years ago)
- Branches:
- 6.1, 6.1.1
- Children:
- fd698d8
- Parents:
- d47f763
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
rd47f763 r01fd09f 83 83 </listitem> 84 84 85 <listitem><para>April 16, 2005 [matt]: Reword handling of hotpluggable devices 86 now that we install the hotplug package (Andrew Benton)</para></listitem> 87 85 88 <listitem><para>April 16, 2005 [matt]: Minor wording/typo fixes (Allard Welter) 86 89 </para></listitem> -
chapter07/udev.xml
rd47f763 r01fd09f 155 155 be called upon to create the relevant device node(s) according to the 156 156 <systemitem class="filesystem">sysfs</systemitem> data available in 157 <filename class="directory">/sys</filename>. If the driver for the 158 just plugged in device is available as a module but currently unloaded, 159 then attaching the device to the system will only cause the kernel's 160 bus driver to generate a hotplug event that notifies userspace of the 161 new device connection and it not being attached to a driver. In 162 effect, nothing happens and the device itself is not usable 163 yet.</para> 164 165 <para>If building a system that has a lot of drivers compiled as 166 modules rather than directly built into the kernel, using the 167 <command>S05modules</command> may not be practical. The Hotplug 168 package (see <ulink url="http://linux-hotplug.sourceforge.net/"/>) can 169 be beneficial in these cases. When the Hotplug package is installed, 170 it will respond to the aforementioned kernel's bus driver hotplug 171 events. The Hotplug package will load the appropriate module and make 172 this device available by creating the device node(s) for it.</para> 157 <filename class="directory">/sys</filename>.</para> 158 159 <para>If the driver for the just plugged in device is available as a module but 160 currently unloaded, the Hotplug package will load the appropriate module 161 and make this device available by creating the device node(s) for it.</para> 173 162 </sect2> 174 163
Note:
See TracChangeset
for help on using the changeset viewer.