Changeset 61e63d3 for chapter07/udev.xml
- Timestamp:
- 05/23/2008 01:45:45 AM (16 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, 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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 9faa3e2
- Parents:
- 1c6f1c1
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/udev.xml
r1c6f1c1 r61e63d3 106 106 class="directory">/dev</filename>. This is necessary because some devices, 107 107 directories, and symlinks are needed before the dynamic device handling 108 processes are available during the early stages of booting a system .109 Creating static device nodes in <filename110 class="directory">/lib/udev/devices</filename> also provides an easy111 workaround for devices that are not supported by the dynamic device112 handling infrastructure. The bootscript then starts the Udev daemon,113 <command>udevd</command>, which will act on any uevents it receives.114 Finally, the bootscript forces the kernel to replay uevents for any115 devices that have already been registered and then waits for108 processes are available during the early stages of booting a system, or 109 are required by <command>udevd</command> itself. Creating static device 110 nodes in <filename class="directory">/lib/udev/devices</filename> also 111 provides an easy workaround for devices that are not supported by the 112 dynamic device handling infrastructure. The bootscript then starts the 113 Udev daemon, <command>udevd</command>, which will act on any uevents it 114 receives. Finally, the bootscript forces the kernel to replay uevents for 115 any devices that have already been registered and then waits for 116 116 <command>udevd</command> to handle them.</para> 117 117 … … 156 156 might contain the string 157 157 <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>. 158 The rules that LFS installs will cause <command>udevd</command> to call159 out to <command>/sbin/modprobe</command> with the contents of the160 <envar>MODALIAS</envar> uevent environment variable ( thatshould be the158 The default rules provided with Udev will cause <command>udevd</command> 159 to call out to <command>/sbin/modprobe</command> with the contents of the 160 <envar>MODALIAS</envar> uevent environment variable (which should be the 161 161 same as the contents of the <filename>modalias</filename> file in sysfs), 162 162 thus loading all modules whose aliases match this string after wildcard … … 269 269 example, a poorly-writen rule can match both a SCSI disk (as desired) 270 270 and the corresponding SCSI generic device (incorrectly) by vendor. 271 Find the offending rule and make it more specific.</para> 271 Find the offending rule and make it more specific, with the help of the 272 <command>udevadm info</command> command.</para> 272 273 273 274 </sect3> … … 282 283 <systemitem class="filesystem">sysfs</systemitem> attribute and appending 283 284 it to the <filename>/etc/udev/rules.d/10-wait_for_sysfs.rules</filename> 284 file . Please notify the LFS Development list if you do so and it285 helps.</para>285 file (create this file if it does not exist). Please notify the LFS 286 Development list if you do so and it helps.</para> 286 287 287 288 </sect3>
Note:
See TracChangeset
for help on using the changeset viewer.