X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=NEWS;h=91698d5380aaac6cc7fb5e25fc35c7fcfca19c63;hp=5dafcad1db80c2a18a96fbfa6e997064adc5089a;hb=9379b7c16dd3b2f11d9e69c063706037ae001a0a;hpb=e8c84c98b9452dd1f4fe738f7e12149e0198dff6

diff --git a/NEWS b/NEWS
index 5dafcad1d..91698d538 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,52 @@
+udev 142
+========
+Bugfixes.
+
+Libudev allows to subscribe to udev events. To prevent unwanted messages
+to be delivered, and waking up the subscribing process, a filter can be
+installed, to drop messages inside a kernel socket filter. The filters
+match on the <subsytem>:<devtype> properties of the device.
+    This is part of the ongoing effort to replace HAL, and switch current
+users over to directly use libudev, or for higher-level services use the
+specialized D-Bus interface of a DeviceKit service.
+    Libudev is still marked as experimental, and its interface might
+change if needed, but no major changes of the currently exported interface
+are expected anymore, and a first stable release should happen soon.
+
+A too old kernel (2.6.21) or a kernel with CONFIG_SYSFS_DEPRECATED
+is not supported since while and udevd will log an error message at
+startup.
+
+DVB device naming is supplied by the kernel now. In case older kernels
+need to be supported, the old shell script should be added to a compat
+rules file.
+
+udev 141
+========
+Bugfixes.
+
+The processed udev events get send back to the netlink socket. Libudev
+provides access to these events. This is work-in-progress, to replace
+the DeviceKit daemon functionality directly with libudev. There are
+upcoming kernel changes to allow non-root users to subcribe to these
+events.
+
+udev 140
+========
+Bugfixes.
+
+"udevadm settle" now optionally accepts a range of events to wait for,
+instead of waiting for "all" events.
+
+udev 139
+========
+Bugfixes.
+
+The installed watch for block device metadata changes is now removed
+during event hadling, because some (broken) tools may be called from udev
+rules and (wrongly) open the device with write access. After the finished
+event handling the watch is restored.
+
 udev 138
 ========
 Bugfixes.