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

Reindl Harald h.reindl at thelounge.net
Tue Feb 11 08:34:14 PST 2014

Am 11.02.2014 17:29, schrieb Andrey Borzenkov:
> В Tue, 11 Feb 2014 17:20:15 +0100
> "Jason A. Donenfeld" <Jason at zx2c4.com> пишет:
>> 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?
> /run is used to pass state between initrd and system for such
> components as udev or mdadm. I do not know how your initramfs
> implementation works and whether it is using udev, but if you support
> root on MD, you likely will need /run

in context systemd maybe, in context MD not

the machine in front of me running F20 with systemd has root
on RAID10 originally installed with F14 before /run and systemd
existed in the setup

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140211/59948509/attachment.pgp>

More information about the systemd-devel mailing list