summaryrefslogtreecommitdiff
path: root/RELEASE-NOTES
diff options
context:
space:
mode:
authorKay Sievers <kay.sievers@suse.de>2006-09-06 22:18:04 +0200
committerKay Sievers <kay.sievers@suse.de>2006-09-06 22:18:04 +0200
commit4a51530993e28c9a689be535fd1d34b259b39f2a (patch)
treec2a402265c7432f259ce6ec45d72866639531f48 /RELEASE-NOTES
parent0b07eaa0837516e84b3e804a3af3307ab57b0ed0 (diff)
release 099
Diffstat (limited to 'RELEASE-NOTES')
-rw-r--r--RELEASE-NOTES21
1 files changed, 21 insertions, 0 deletions
diff --git a/RELEASE-NOTES b/RELEASE-NOTES
index 9fe4542dd5..c7e7a053ea 100644
--- a/RELEASE-NOTES
+++ b/RELEASE-NOTES
@@ -1,3 +1,24 @@
+udev 099
+========
+Bugfixes.
+
+Udevtrigger can now filter the list of devices to be triggered. Matches
+for subsystems or sysfs attributes can be specified.
+
+The entries in /dev/.udev/queue and /dev/.udev/failed have changed to
+zero-sized files to avoid pointing to /sys and confuse broken tools which
+scan the /dev directory. To retry failed events, udevtrigger --retry-failed
+should be used now.
+
+The rules and scripts to create udev rules for persistent network
+devices and optical drives are in the extras/rules_generator directory
+now. If you use something similar, please consider replacing your own
+version with this, to share the support effort. The rule_generator
+installs its own rules into /etc/udev/rules.d.
+
+The cdrom_id tool installs its own rule now in /etc/udev/rules.d, cause
+the rule_generator depends on cdrom_id to be called in an earlier rule.
+
udev 098
========
Bugfixes.