- Timestamp:
- 06/24/2004 02:27:04 PM (20 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- e43d9b66
- Parents:
- ad6dca1
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/hotplug.xml
rad6dca1 r3f91a9c 12 12 <sect2 role="package"><title/> 13 13 14 <para>The Hotplug package contains scripts that react upon various changes 15 in the kernel state, in particular, addition and removal of hardware. This 16 package also detects existing hardware during boot and inserts the relevant 17 modules into the running kernel. 14 <para>The Hotplug package contains scripts that react upon hotplug events 15 generated by the kernel. Such events correspond to every change in the 16 in the kernel state visible in the "sysfs" filesystem, e.g., the addition and 17 removal of hardware. This package also detects existing hardware during 18 boot and inserts the relevant modules into the running kernel. 18 19 </para> 19 20 <segmentedlist> … … 29 30 30 31 <para> 31 Apply the patch that avoids bogus dependencies of the 32 <command>usb.rc</command> script 33 upon <application>which</application> and 34 <application>usbutils</application> packages: 32 The <command>usb.rc</command> script provided by the 33 <application>Hotplug</application> package depends on the programs 34 <command>usbutils</command> and <command>which</command> being present. 35 However, these programs are not called for any useful purpose. 36 Apply the patch that removes those dependencies: 35 37 </para> 36 38 … … 38 40 39 41 <para> 40 USB coldplugging is somewhat broken in Hotplug by default. Fix this with the 41 following patch: 42 USB coldplugging is somewhat broken in <application>Hotplug</application> 43 by default: the DEVICE environment variable is not passed to user-defined USB 44 hotplug handlers. Fix this with the following patch: 42 45 </para> 43 46 44 47 <screen><userinput>patch -Np1 -i ../hotplug-&hotplug-version;-device-2.patch</userinput></screen> 45 48 49 <!-- Waiting for hotplug-2004_04_01-isapnp-4.patch 46 50 <para> 47 At last, there is an optional patch that adds ISAPNP hardware detection48 capabilities to Hotplug. It is not well tested . If you chose to apply it,49 run the following command:51 There is an optional patch that adds ISAPNP hardware detection 52 capabilities to Hotplug. It is not well tested and in fact contains known 53 bugs. If you chose to apply it, run the following command: 50 54 </para> 51 55 52 56 <screen><userinput>patch -Np1 -i ../hotplug-&hotplug-version;-isapnp-2.patch</userinput></screen> 57 --> 53 58 54 55 <para>And finally install the Hotplug package:</para> 59 <para>Now install the Hotplug package:</para> 56 60 57 61 <screen><userinput>make install</userinput></screen> … … 62 66 <screen><userinput>rm -rf /etc/init.d</userinput></screen> 63 67 68 <para>Network device hotplugging is not supported by LFS bootscripts yet. For 69 that reason, remove the network hotplug agent:</para> 70 71 <screen><userinput>rm -f /etc/hotplug/net.agent</userinput></screen> 72 <!-- Will be useless with version 4 of the isapnp patch 64 73 <para> 65 74 If you have applied the ISAPNP patch, add some required entries to … … 82 91 since Marco d'Itri will try to convince developers to put them into the 83 92 corresponding modules themselves.</para> 84 93 --> 85 94 </sect2> 86 95 … … 110 119 from the lfs-bootscripts package. 111 120 The <command>*.rc</command> 112 scripts try to find kernel modules corresponding to your hardware and insert113 them into the runningkernel.121 scripts try to recover hotplug events that were lost during system boot 122 because, e.g., the root filesystem was not mounted by the kernel. 114 123 </para> 115 124 </listitem> … … 180 189 sortas="e-/etc/hotplug.d">/etc/hotplug.d</primary></indexterm> 181 190 <para>This directory contains programs (or symlinks to them) 182 that are interested in receiving allhotplug events. E.g.,191 that are interested in receiving hotplug events. E.g., 183 192 <application>udev</application> puts its symlink here during installation. 184 193 </para>
Note:
See TracChangeset
for help on using the changeset viewer.