Changeset 360fdfca for chapter09/udev.xml
- Timestamp:
- 01/26/2024 05:28:53 PM (5 months ago)
- Branches:
- 12.1, 12.1-rc1, multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.1, xry111/mips64el, xry111/update-glibc
- Children:
- 0d80918a, f6a43f6
- Parents:
- 44850bb
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter09/udev.xml
r44850bb r360fdfca 130 130 supported by a module. For example, the <emphasis>snd-fm801</emphasis> 131 131 driver supports PCI devices with vendor ID 0x1319 and device ID 0x0801, 132 and has an alias of < quote>pci:v00001319d00000801sv*sd*bc04sc01i*</quote>.132 and has an alias of <literal>pci:v00001319d00000801sv*sd*bc04sc01i*</literal>. 133 133 For most devices, the bus driver exports the alias of the driver that 134 134 would handle the device via <systemitem … … 136 136 <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file 137 137 might contain the string 138 < quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>.138 <literal>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</literal>. 139 139 The default rules provided with udev will cause <command>udevd</command> 140 140 to call out to <command>/sbin/modprobe</command> with the contents of the … … 302 302 <para>This is due to the fact that udev, by design, handles uevents and 303 303 loads modules in parallel, and thus in an unpredictable order. This will 304 never be <quote>fixed </quote>.You should not rely upon the kernel device304 never be <quote>fixed.</quote> You should not rely upon the kernel device 305 305 names being stable. Instead, create your own rules that make symlinks with 306 306 stable names based on some stable attributes of the device, such as a
Note:
See TracChangeset
for help on using the changeset viewer.