[systemd-devel] /run needs to be mounted? ugh.

Lennart Poettering lennart at poettering.net
Tue Feb 11 09:32:58 PST 2014

On Tue, 11.02.14 18:08, Jason A. Donenfeld (Jason at zx2c4.com) wrote:

> On Tue, Feb 11, 2014 at 5:25 PM, Lennart Poettering
> <lennart at poettering.net> wrote:
> > An initrd without /run is mostly pointless, no? Either you have storage
> > daemons and hence need /run around, or you don't have storage daemons,
> > in which case you can just boot without involving any initrd?
> In my use of an initrd, I just use cryptsetup, which AFAIK, isn't a
> storage daemon but rather reads the LUKS header, determines the key,
> and calls the ioctl to get it mapped. In this case, all the 'state'
> remains in the kernel, and thus doesn't require /run.

Hmm, so how do you wait for the LUKS device to show up? You need
something like udev around, which uses /run...

And AFAIR the DM userspace does keep some runtime state around, and that
one probably wants to pass over to the host OS...


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list