Author: bryan
Date: 2006-10-04 16:40:41 -0600 (Wed, 04 Oct 2006)
New Revision: 7820
Modified:
trunk/udev-config/05-udev-early.rules
trunk/udev-config/ChangeLog
trunk/udev-config/doc/05-udev-early.txt
Log:
Remove WAIT_FOR_SYSFS="bus" rule; it is no longer required in kernel 2.6.18.
Update docs to match.
Modified: trunk/udev-config/05-udev-early.rules
===================================================================
--- trunk/udev-config/05-udev-early.rules 2006-10-04 18:03:23 UTC (rev
7819)
+++ trunk/udev-config/05-udev-early.rules 2006-10-04 22:40:41 UTC (rev
7820)
@@ -1,3 +1,2 @@
# sysfs is populated after the event is sent
-ACTION=="add", DEVPATH=="/devices/*", SUBSYSTEMS=="?*", WAIT_FOR_SYSFS="bus"
ACTION=="add", SUBSYSTEM=="scsi", WAIT_FOR_SYSFS="ioerr_cnt"
Modified: trunk/udev-config/ChangeLog
===================================================================
--- trunk/udev-config/ChangeLog 2006-10-04 18:03:23 UTC (rev 7819)
+++ trunk/udev-config/ChangeLog 2006-10-04 22:40:41 UTC (rev 7820)
@@ -1,3 +1,9 @@
+2006-10-04 Bryan Kadzban <[EMAIL PROTECTED]>
+ * 05-udev-early.rules: Remove WAIT_FOR_SYSFS="bus" rule. With kernel
+ 2.6.18, this rule is no longer required.
+
+ * doc/05-udev-early.txt: Update to match.
+
2006-09-28 Bryan Kadzban <[EMAIL PROTECTED]>
* doc/60-persistent-storage.txt: Explain persistent storage rules, or
at least the parts I understand. (I don't use DASD or netblock or
Modified: trunk/udev-config/doc/05-udev-early.txt
===================================================================
--- trunk/udev-config/doc/05-udev-early.txt 2006-10-04 18:03:23 UTC (rev
7819)
+++ trunk/udev-config/doc/05-udev-early.txt 2006-10-04 22:40:41 UTC (rev
7820)
@@ -14,21 +14,20 @@
All rules in this file match ACTION="add", because none of them apply when
devices are being removed.
-DEVPATH is the sysfs path to the kobject that this uevent is for. /devices/*
-corresponds to /sys/devices/* in the filesystem, because udev uses /sys as
-its root directory.
+SUBSYSTEM is the kernel subsystem that the device uses. Current kernels have
+some issues with SCSI device attributes being created too late. For any device
+with a SUBSYSTEM of scsi, we must wait for the ioerr_cnt attribute. (This is
+the last attribute created for SCSI devices, so when this attribute appears,
+the kobject is fully populated.)
-SUBSYSTEMS searches up the device tree for a SUBSYSTEM value that matches the
-string given. SUBSYSTEM is the kernel subsystem that the device uses, see
-below. In this rule, we use ?*, which matches any non-empty value. (Note: the
-device tree is not necessarily the same as the DEVPATH. "Up the device tree"
-is the same path followed by udevinfo when it is given the argument "-a".)
+It is also possible to use SUBSYSTEMS in Udev rules. Using SUBSYSTEMS would
+cause Udev to search up the device tree for a matching SUBSYSTEM value. (Note
+that "the device tree" is not necessarily the same as the path under /sys (the
+DEVPATH). Rather, "up the device tree" is the path followed by udevinfo when
+it is given the argument "-a".)
-When the SUBSYSTEMS value is non-empty, we know that a "bus" attribute will be
-created eventually, so we wait for it here. This attribute is required for
-some rules and programs.
+We do not use SUBSYSTEMS in this rule, because we only care about the SUBSYSTEM
+of the kobject in question. We don't care about devices that are children of
+SCSI devices, only the SCSI device itself. We will use SUBSYSTEMS in later
+rules, though.
-Also, current kernels have some issues with SCSI device attributes being
-created too late. For any device with a SUBSYSTEM of scsi, we wait for the
-ioerr_cnt attribute. (This is the last attribute created on SCSI devices.)
-
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
