On Fri, Mar 25, 2011 at 7:07 AM, Kay Sievers <kay.siev...@vrfy.org> wrote: > Instead of the /dev/.run trick we have currently implemented, we decided > to move the early-boot runtime dir to /run. >
What is the benefit? /var/run is well known and established; what is the reason to move it in another place? [...] > /* Abstract namespace! */ > -#define LOGGER_SOCKET "/dev/.run/systemd/logger" > +#define LOGGER_SOCKET "/run/systemd/logger" > They are not really abstract sockets anymore, are not they? (Not really related, but just wanted to confirm) [...] > diff --git a/tmpfiles.d/systemd.conf b/tmpfiles.d/systemd.conf > index 880a6ed..2d8e520 100644 > --- a/tmpfiles.d/systemd.conf > +++ b/tmpfiles.d/systemd.conf > @@ -7,9 +7,10 @@ > > # See tmpfiles.d(5) for details > > -d /var/lock/subsys 0755 root root - > -d /var/run/user 0755 root root 10d > -F /var/run/utmp 0664 root utmp - > +d /run/lock 0755 root lock - > +d /run/lock/subsys 0755 root root - > +d /run/user 0755 root root 10d > +F /run/utmp 0664 root utmp - > f /var/log/wtmp 0664 root utmp - > f /var/log/btmp 0600 root utmp - > Please, no. When it runs, /var/run should be equivalent of /run (or whatever). If it is not - distribution has reasons to not do it; not everyone can switch to tmpfs overnight. Leave it at /var/run as to not break existing setups. It will work for both cases. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
