Typo and rewording of hotplug filelist

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4758 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Matthew Burgess 2005-03-14 20:30:17 +00:00
parent 722f0a4e8b
commit c59fe13219
2 changed files with 23 additions and 25 deletions

View File

@ -82,6 +82,9 @@ first a summary, then a detailed log.</para>
</itemizedlist>
</listitem>
<listitem><para>March 14, 2005 [matt]: Fix typos, and reword some of the hotplug explanations for (hopefully) improved clarity</para>
</listitem>
<listitem><para>March 14, 2005 [matt]: Upgraded to gettext-0.14.3</para>
</listitem>

View File

@ -85,7 +85,7 @@ directory:</para>
<listitem>
<indexterm zone="ch-system-hotplug hotplug"><primary
sortas="b-hotplug">hotplug</primary></indexterm>
<para>This script is called by default by Linux kernel when something
<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>
</listitem>
</varlistentry>
@ -95,14 +95,12 @@ changes in its internal state (e.g., a new device is added or removed).</para>
<listitem>
<indexterm zone="ch-system-hotplug hotplug-rc"><primary
sortas="d-/etc/hotplug/*.rc">/etc/hotplug/*.rc</primary></indexterm>
<para>These scripts are used for cold plugging, i.e., detection and other
specific actions upon 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, e.g., the root filesystem was not mounted by the kernel.
</para>
<para>These scripts are used for cold plugging, i.e., detecting and acting upon
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>
</listitem>
</varlistentry>
@ -113,8 +111,8 @@ because, e.g., the root filesystem was not mounted by the kernel.
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 user-provided
scripts, if any.
Their action is to insert corresponding kernel modules and call any
user-provided scripts.
</para>
</listitem>
</varlistentry>
@ -124,7 +122,7 @@ scripts, if any.
<listitem>
<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 Hotplug
<para>This file contains common functions used by other scripts in the Hotplug
package.
</para>
</listitem>
@ -135,8 +133,8 @@ package.
<listitem>
<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 hotplug scripts.
<para>This file contains the list of modules that should never be inserted into
the kernel by the hotplug scripts.
</para>
</listitem>
</varlistentry>
@ -146,8 +144,7 @@ inserted into the kernel by hotplug scripts.
<listitem>
<indexterm zone="ch-system-hotplug hotplug-subdirs"><primary
sortas="e-/etc/hotplug/{pci,usb}">/etc/hotplug/{pci,usb}</primary></indexterm>
<para>These directories are supposed to contain user-written handlers for
hotplug events.
<para>These directories contain user-written handlers for hotplug events.
</para>
</listitem>
</varlistentry>
@ -158,7 +155,7 @@ hotplug events.
<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.
call for each USB device, based on its vendor ID and other attributes.
</para>
</listitem>
</varlistentry>
@ -168,7 +165,7 @@ call for each USB device, based on its vendor, id and other attributes.
<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 since bootup that hotplug has called.
<para>This file contains all the events that hotplug has called since bootup.
</para>
</listitem>
</varlistentry>
@ -178,10 +175,9 @@ sortas="e-/var/log/hotplug/events">/var/log/hotplug/events</primary></indexterm>
<listitem>
<indexterm zone="ch-system-hotplug hotplug-hotplug.d"><primary
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. E.g.,
<application>Udev</application> puts its symlink here during installation.
</para>
<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>
</listitem>
</varlistentry>
@ -190,9 +186,8 @@ that are interested in receiving hotplug events. E.g.,
<listitem>
<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 there firmware loaded before use.
</para>
<para>This directory contains the firmware for devices that need to have their
firmware loaded before use.</para>
</listitem>
</varlistentry>