[systemd-devel] use /run instead of /dev/.run

Kay Sievers kay.sievers at vrfy.org
Mon Mar 28 15:21:20 PDT 2011

On Tue, Mar 29, 2011 at 00:11, Jan Engelhardt <jengelh at medozas.de> wrote:
> On Monday 2011-03-28 23:55, Lennart Poettering wrote:
>>On Mon, 28.03.11 23:46, Jan Engelhardt (jengelh at medozas.de) wrote:
>>> On Monday 2011-03-28 23:04, Lennart Poettering wrote:
>>> >On Fri, 25.03.11 05:07, Kay Sievers (kay.sievers at vrfy.org) wrote:
>>> >
>>> >> Instead of the /dev/.run trick we have currently implemented, we decided
>>> >> to move the early-boot runtime dir to /run.
>>> >
>>> >Applied (and fixed a few minor issues).
>>> Uhm, *cough*. There are a handful of dot-dirs in /dev, such as
>>> .sysconfig (seems to be my distro), .systemd, and .udev. Now util-linux
>>> 2.19 has also started using a directory in /dev, namely .mount.
>>> And now /run gets a non-standard exception?
>>It's the other way round.
>>We want to get rid of the hidden-files-in-/dev mess. Hence all those
>>dirs will move to /run/ and /var/run will simply point to that.
> Ok that makes sense. But will /run stick around after initramfs is
> done mounting & pivoting around?

Yeah, it is supposed to mount a tmpfs there and then move it to the real root.

> If so, what does LSB say to this new directory?

Nothing really, they just document current common practice. We might
request an update to LSB after it is used for a while and has shown
that it is what we want.


More information about the systemd-devel mailing list