On Tue, 11.02.14 17:20, Jason A. Donenfeld (ja...@zx2c4.com) wrote: > > On Tue, Feb 11, 2014 at 5:15 PM, Dave Reisner <d...@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 -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
