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

Lennart Poettering lennart at poettering.net
Tue Feb 11 08:25:29 PST 2014

On Tue, 11.02.14 17:20, Jason A. Donenfeld (Jason at zx2c4.com) wrote:

> On Tue, Feb 11, 2014 at 5:15 PM, Dave Reisner <d at falconindy.com> wrote:
> > I don't think there's any change needed here. The interface states:
> >
> >   "The initrd should mount /run as a tmpfs".
> > And sure enough, this isn't a requirement, but there's many valid
> > reasons to do this.
> Ahh, okay. I suppose what I'm wondering is what the advantages are to
> mounting /run (if the remaining interfaces in the list aren't used)?
> It looks like mounting /run occurs pretty soon in core/main.c. Could
> it be that the only advantages of mounting /run early on are for using
> the more advanced systemd initrd interfaces, such as giving control
> back during shutdown? Or are there benefits in doing this even for the
> most minimal of initrd?

Well, most storage daemons want to store runtime info in /run, and make
sure it is passed to the main OS. 

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?


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list