Various hotplug-related changes

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3848 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Alexander E. Patrakov 2004-06-24 14:27:04 +00:00
parent ad6dca11ed
commit 3f91a9cef2
4 changed files with 38 additions and 21 deletions

View File

@ -78,6 +78,12 @@ first a summary, then a detailed log.</para>
</itemizedlist> </itemizedlist>
</listitem> </listitem>
<listitem><para>June 24, 2004 [alexander]: Wordings changed on the hotplug
page</para></listitem>
<listitem><para>June 24, 2004 [alexander]: Removed hotplug isapnp patch for a
while until bugs are fixed</para></listitem>
<listitem><para>June 23, 2004 [matt]: Removed the note regarding the use of <listitem><para>June 23, 2004 [matt]: Removed the note regarding the use of
GRUB's --no-mem-option</para></listitem> GRUB's --no-mem-option</para></listitem>

View File

@ -77,12 +77,14 @@ following:</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<!--
<varlistentry> <varlistentry>
<term>Hotplug ISAPNP Coldplugging Patch - 1 KB:</term> <term>Hotplug ISAPNP Coldplugging Patch - 1 KB:</term>
<listitem> <listitem>
<para><ulink url="&patches-root;hotplug-&hotplug-version;-isapnp-2.patch"/></para> <para><ulink url="&patches-root;hotplug-&hotplug-version;-isapnp-2.patch"/></para>
</listitem> </listitem>
</varlistentry> </varlistentry>
-->
<varlistentry> <varlistentry>
<term>Inetutils Kernel Headers Patch - 1 KB:</term> <term>Inetutils Kernel Headers Patch - 1 KB:</term>

View File

@ -11,10 +11,11 @@
<sect2 role="package"><title/> <sect2 role="package"><title/>
<para>The Hotplug package contains scripts that react upon various changes <para>The Hotplug package contains scripts that react upon hotplug events
in the kernel state, in particular, addition and removal of hardware. This generated by the kernel. Such events correspond to every change in the
package also detects existing hardware during boot and inserts the relevant in the kernel state visible in the "sysfs" filesystem, e.g., the addition and
modules into the running kernel. removal of hardware. This package also detects existing hardware during
boot and inserts the relevant modules into the running kernel.
</para> </para>
<segmentedlist> <segmentedlist>
<segtitle>&buildtime;</segtitle> <segtitle>&buildtime;</segtitle>
@ -28,31 +29,34 @@ modules into the running kernel.
<title>Installation of Hotplug</title> <title>Installation of Hotplug</title>
<para> <para>
Apply the patch that avoids bogus dependencies of the The <command>usb.rc</command> script provided by the
<command>usb.rc</command> script <application>Hotplug</application> package depends on the programs
upon <application>which</application> and <command>usbutils</command> and <command>which</command> being present.
<application>usbutils</application> packages: However, these programs are not called for any useful purpose.
Apply the patch that removes those dependencies:
</para> </para>
<screen><userinput>patch -Np1 -i ../hotplug-&hotplug-version;-bogus_deps-1.patch</userinput></screen> <screen><userinput>patch -Np1 -i ../hotplug-&hotplug-version;-bogus_deps-1.patch</userinput></screen>
<para> <para>
USB coldplugging is somewhat broken in Hotplug by default. Fix this with the USB coldplugging is somewhat broken in <application>Hotplug</application>
following patch: by default: the DEVICE environment variable is not passed to user-defined USB
hotplug handlers. Fix this with the following patch:
</para> </para>
<screen><userinput>patch -Np1 -i ../hotplug-&hotplug-version;-device-2.patch</userinput></screen> <screen><userinput>patch -Np1 -i ../hotplug-&hotplug-version;-device-2.patch</userinput></screen>
<!-- Waiting for hotplug-2004_04_01-isapnp-4.patch
<para> <para>
At last, there is an optional patch that adds ISAPNP hardware detection There is an optional patch that adds ISAPNP hardware detection
capabilities to Hotplug. It is not well tested. If you chose to apply it, capabilities to Hotplug. It is not well tested and in fact contains known
run the following command: bugs. If you chose to apply it, run the following command:
</para> </para>
<screen><userinput>patch -Np1 -i ../hotplug-&hotplug-version;-isapnp-2.patch</userinput></screen> <screen><userinput>patch -Np1 -i ../hotplug-&hotplug-version;-isapnp-2.patch</userinput></screen>
-->
<para>Now install the Hotplug package:</para>
<para>And finally install the Hotplug package:</para>
<screen><userinput>make install</userinput></screen> <screen><userinput>make install</userinput></screen>
@ -61,6 +65,11 @@ the script including with LFS-Bootscripts:</para>
<screen><userinput>rm -rf /etc/init.d</userinput></screen> <screen><userinput>rm -rf /etc/init.d</userinput></screen>
<para>Network device hotplugging is not supported by LFS bootscripts yet. For
that reason, remove the network hotplug agent:</para>
<screen><userinput>rm -f /etc/hotplug/net.agent</userinput></screen>
<!-- Will be useless with version 4 of the isapnp patch
<para> <para>
If you have applied the ISAPNP patch, add some required entries to If you have applied the ISAPNP patch, add some required entries to
<filename>/etc/modprobe.conf</filename>:</para> <filename>/etc/modprobe.conf</filename>:</para>
@ -81,7 +90,7 @@ EOF</userinput></screen>
<para>These entries may not be needed in newer versions of the Linux kernel, <para>These entries may not be needed in newer versions of the Linux kernel,
since Marco d'Itri will try to convince developers to put them into the since Marco d'Itri will try to convince developers to put them into the
corresponding modules themselves.</para> corresponding modules themselves.</para>
-->
</sect2> </sect2>
@ -109,8 +118,8 @@ specific actions upon hardware already present during system startup.
They are called by the <filename>hotplug</filename> initscript that comes They are called by the <filename>hotplug</filename> initscript that comes
from the lfs-bootscripts package. from the lfs-bootscripts package.
The <command>*.rc</command> The <command>*.rc</command>
scripts try to find kernel modules corresponding to your hardware and insert scripts try to recover hotplug events that were lost during system boot
them into the running kernel. because, e.g., the root filesystem was not mounted by the kernel.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -179,7 +188,7 @@ call for each USB device, based on its vendor, id and other attributes.
<indexterm zone="ch-system-hotplug hotplug-hotplug.d"><primary <indexterm zone="ch-system-hotplug hotplug-hotplug.d"><primary
sortas="e-/etc/hotplug.d">/etc/hotplug.d</primary></indexterm> sortas="e-/etc/hotplug.d">/etc/hotplug.d</primary></indexterm>
<para>This directory contains programs (or symlinks to them) <para>This directory contains programs (or symlinks to them)
that are interested in receiving all hotplug events. E.g., that are interested in receiving hotplug events. E.g.,
<application>udev</application> puts its symlink here during installation. <application>udev</application> puts its symlink here during installation.
</para> </para>
</listitem> </listitem>

View File

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?> <?xml version="1.0" encoding="ISO-8859-1"?>
<!ENTITY version "SVN-20040623"> <!ENTITY version "SVN-20040624">
<!ENTITY releasedate "June 23, 2004"> <!ENTITY releasedate "June 24, 2004">
<!ENTITY milestone "6.0"> <!ENTITY milestone "6.0">
<!ENTITY lfs-root "http://www.linuxfromscratch.org/"> <!ENTITY lfs-root "http://www.linuxfromscratch.org/">