Changeset edbeeb5 for chapter07/udev.xml
- Timestamp:
- 11/03/2015 03:48:42 AM (8 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, 7.9, 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:
- c81b68d
- Parents:
- 7bbd1bd
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/udev.xml
r7bbd1bd redbeeb5 252 252 253 253 <para>This usually happens if a rule unexpectedly matches a device. For 254 example, a poorly-writ en rule can match both a SCSI disk (as desired)254 example, a poorly-written rule can match both a SCSI disk (as desired) 255 255 and the corresponding SCSI generic device (incorrectly) by vendor. 256 256 Find the offending rule and make it more specific, with the help of the
Note:
See TracChangeset
for help on using the changeset viewer.