units: introduce network-pre.target as place to hook in firewalls

[elogind.git] / NEWS

diff --git a/NEWS b/NEWS
index 057a04fbeeac026566f70edfcd6359c60bcdcfaa..8a022bea78d9a5ae3ddce56ec2cac9e4d1cfe18b 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,22 @@
 systemd System and Service Manager
 
+CHANGES WITH 214:
+
+        * As an experimental feature, udev now tries to lock the
+          disk device node (flock(LOCK_SH|LOCK_NB)) while it
+          executes events for the disk or any of its partitions.
+          Applications like partitioning programs can lock the
+          disk device node (flock(LOCK_EX)) and claim temporary
+          device ownership that way; udev will entirely skip all event
+          handling for this disk and its partitions. If the disk
+          was opened for writing, the close will trigger a partition
+          table rescan in udev's "watch" facility, and if needed
+          synthesize "change" events for the disk and all its partions.
+          This is now unconditionally enabled, if it turns out to
+          cause major problems, we might turn it on only for specific
+          devices, or might need to disable it entirely. Device-mapper
+          devices are excluded from this logic.
+
 CHANGES WITH 213:
 
         * A new "systemd-timesyncd" daemon has been added for
@@ -7,8 +24,8 @@ CHANGES WITH 213:
           implements an SNTP client. In contrast to NTP
           implementations such as chrony or the NTP reference server
           this only implements a client side, and does not bother with
-          the full NTP complexity, focusing only on querying time
-          from one remote server and synchronizing the local clock to
+          the full NTP complexity, focusing only on querying time from
+          one remote server and synchronizing the local clock to
           it. Unless you intend to serve NTP to networked clients or
           want to connect to local hardware clocks this simple NTP
           client should be more than appropriate for most
@@ -20,7 +37,9 @@ CHANGES WITH 213:
           early at bootup, in order to accommodate for systems that
           lack an RTC such as the Raspberry Pi and embedded devices,
           and make sure that time monotonically progresses on these
-          systems, even if it is not always correct.
+          systems, even if it is not always correct. To make use of
+          this daemon a new system user and group "systemd-timesync"
+          needs to be created on installation of systemd.
 
         * The queue "seqnum" interface of libudev has been disabled, as
           it was generally incompatible with device namespacing as