gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-05 22:04:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

Ported r4899 from trunk: Tags and text corrections.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.1/BOOK@4900 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Manuel Canales Esparcia 2005-04-11 18:58:13 +00:00
parent 5dd601f3df
commit b03f551529
1 changed files with 13 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
chapter06/hotplug.xml
View File

@ -54,7 +54,8 @@ that reason, remove the network hotplug agent:</para>
<screen><userinput>touch /var/log/hotplug/events</userinput></screen>
<para>Create a directory for storing firmware that can be loaded by hotplug:</para>
<para>Create a directory for storing firmware that can be loaded by
<command>hotplug</command>:</para>
<screen><userinput>mkdir /lib/firmware</userinput></screen>
@ -83,7 +84,7 @@ that reason, remove the network hotplug agent:</para>
<indexterm zone="ch-system-hotplug hotplug"><primary
sortas="b-hotplug">hotplug</primary></indexterm>
<para>This script is called by default by the Linux kernel when something
changes in its internal state (e.g., a new device is added or removed).</para>
changes in its internal state (e.g., a new device is added or removed)</para>
</listitem>
</varlistentry>
@ -97,7 +98,7 @@ 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 recover hotplug events that
were lost during system boot because, for example, the root filesystem was not
mounted by the kernel.</para>
mounted by the kernel</para>
</listitem>
</varlistentry>
@ -109,8 +110,7 @@ sortas="d-/etc/hotplug/*.agent">/etc/hotplug/*.agent</primary></indexterm>
<para>These scripts are called by <command>hotplug</command>
in response to different types of hotplug events generated by the kernel.
Their action is to insert corresponding kernel modules and call any
user-provided scripts.
</para>
user-provided scripts</para>
</listitem>
</varlistentry>
@ -120,8 +120,7 @@ user-provided scripts.
<indexterm zone="ch-system-hotplug hotplug-blacklist"><primary
sortas="e-/etc/hotplug/blacklist">/etc/hotplug/blacklist</primary></indexterm>
<para>This file contains the list of modules that should never be inserted into
the kernel by the hotplug scripts.
</para>
the kernel by the Hotplug scripts</para>
</listitem>
</varlistentry>
@ -131,8 +130,7 @@ the kernel by the hotplug scripts.
<indexterm zone="ch-system-hotplug hotplug-functions"><primary
sortas="e-/etc/hotplug/hotplug.functions">/etc/hotplug/hotplug.functions</primary></indexterm>
<para>This file contains common functions used by other scripts in the Hotplug
package.
</para>
package</para>
</listitem>
</varlistentry>
@ -141,8 +139,7 @@ package.
<listitem>
<indexterm zone="ch-system-hotplug hotplug-subdirs"><primary
sortas="e-/etc/hotplug/{pci,usb}">/etc/hotplug/{pci,usb}</primary></indexterm>
<para>These directories contain user-written handlers for hotplug events.
</para>
<para>These directories contain user-written handlers for hotplug events</para>
</listitem>
</varlistentry>
@ -152,8 +149,7 @@ sortas="e-/etc/hotplug/{pci,usb}">/etc/hotplug/{pci,usb}</primary></indexterm>
<indexterm zone="ch-system-hotplug hotplug-usb.usermap"><primary
sortas="e-/etc/hotplug/usb.usermap">/etc/hotplug/usb.usermap</primary></indexterm>
<para>This file contains rules that determine which user-defined handlers to
call for each USB device, based on its vendor ID and other attributes.
</para>
call for each USB device, based on its vendor ID and other attributes</para>
</listitem>
</varlistentry>
@ -164,7 +160,7 @@ call for each USB device, based on its vendor ID and other attributes.
sortas="e-/etc/hotplug.d">/etc/hotplug.d</primary></indexterm>
<para>This directory contains programs (or symlinks to them) that are interested
in receiving hotplug events. For example, <application>Udev</application> puts
its symlink here during installation.</para>
its symlink here during installation</para>
</listitem>
</varlistentry>
@ -174,7 +170,7 @@ its symlink here during installation.</para>
<indexterm zone="ch-system-hotplug hotplug-firmware"><primary
sortas="e-/lib/firmware">/lib/firmware</primary></indexterm>
<para>This directory contains the firmware for devices that need to have their
firmware loaded before use.</para>
firmware loaded before use</para>
</listitem>
</varlistentry>
@ -183,8 +179,8 @@ firmware loaded before use.</para>
<listitem>
<indexterm zone="ch-system-hotplug hotplug-events"><primary
sortas="e-/var/log/hotplug/events">/var/log/hotplug/events</primary></indexterm>
<para>This file contains all the events that hotplug has called since bootup.
</para>
<para>This file contains all the events that <command>hotplug</command> has
called since bootup</para>
</listitem>
</varlistentry>