tmpfiles: drop /run/lock/lockdev

Hardly any software uses that any more, and better locking mechanisms like
flock() have been available for many years.

Also drop the corresponding "lock" group from sysusers.d/basic.conf.in, as
nothing else is using this.

NEWS

@@ -1,5 +1,18 @@
 systemd System and Service Manager
 
+CHANGES WITH 229:
+
+        * Creation of the legacy /run/lock/lockdev/ directory was
+          dropped from tmpfiles.d/legacy.conf. Hardly any software uses
+          that any more, and better locking mechanisms like flock() have
+          been available for many years. If you still need this, you need to
+          create your own tmpfiles.d config file with:
+            d /run/lock/lockdev 0775 root lock -
+
+        Contributions from: ...
+
+        -- Berlin, 2016-MM-DD
+
 CHANGES WITH 228:
 
         * A number of properties previously only settable in unit

sysusers.d/basic.conf.in

@@ -19,7 +19,6 @@ g wheel   -     -            -
 
 # Access to certain kernel and userspace facilities
 g kmem    -     -            -
-g lock    -     -            -
 g tty     @TTY_GID@     -            -
 g utmp    -     -            -
 

tmpfiles.d/legacy.conf

@@ -18,14 +18,6 @@ L /var/lock - - - - ../run/lock
 
 d /run/lock/subsys 0755 root root -
 
-# /run/lock/lockdev is used to serialize access to tty devices via
-# LCK..xxx style lock files, For more information see:
-# http://lists.freedesktop.org/archives/systemd-devel/2011-March/001823.html
-# On modern systems a BSD file lock is a better choice if
-# serialization is needed on those devices.
-
-d /run/lock/lockdev 0775 root lock -
-
 # /forcefsck, /fastboot and /forcequotacheck are deprecated in favor of the
 # kernel command line options 'fsck.mode=force', 'fsck.mode=skip' and
 # 'quotacheck.mode=force'