Wenn das mal gut geht, ich habe noch nie so einen ausführlichen Changelog Eintrag gelesen, ist nur ein Teil:
sysvinit (2.88dsf-13.3) experimental; urgency=low ▒
▒
[ Roger Leigh ] ▒
* Non-maintainer upload. ▒
* Support for new top-level directory /run to replace /var/run, ▒
/var/lock, /dev/shm and /lib/init/rw as a place to store transient ▒
writable data which should not be preserved across a system ▒
reboot (Closes: #186892, #616571, #620191). /run fixes existing ▒
issues with RAMRUN and RAMLOCK options using tmpfs on /var/run and ▒
/var/lock (Closes: #423405, #481546, #564635, #607136, #620735). ▒
Additionally, /run/shm replaces /dev/shm and may share the same ▒
tmpfs as /run if RAMSHM is set to "no" in /etc/default/rcS. /tmp ▒
may also be configured to be a tmpfs if RAMTMP is set to "yes" in ▒
/etc/default/rcS. /tmp may also be configured to use /run directly if ▒
it is symlinked to /run/tmp, for example. ▒
Summary: ▒
/var/run ??? /run ▒
/var/lock ??? /run/lock ▒
/dev/shm ??? /run/shm ▒
/lib/init/rw ??? /run (not transitioned automatically) ▒
/dev/.* ??? /run (not transitioned automatically) ▒
These changes do not take effect until the system is rebooted as ▒
is currently done for /lib/init/rw setup. Prior to a reboot, the
Ausserdem frage ich mich, wenn /var/run kein eigenes Unterverzeichnis bekommt (zB /run/pid),
wann die ersten Sicherheitsvorfälle kommen durch pid Eiträge, die einfach mal so nach /run/tmp oder /run/shm schwappen ....