Re: systemd: /run directory not created

[Jonathan Liu <net147@gmail.com>]

On 15/04/2013 11:45 PM, Jack Mitchell wrote:
> On 15/04/13 14:10, Martin Jansa wrote:
>> On Mon, Apr 15, 2013 at 01:58:52PM +0100, Jack Mitchell wrote:
>>> Ok, I have just come back to trying out the new systemd implementation,
>>> and this bug still exists.
>>>
>>> Exactly the same error as before:
>>>
>>> [    2.390730] systemd[1]: Failed to mount /run: No such file or 
>>> directory
>>>
>>> Can we shed any light on why this directory is failing to be created 
>>> and
>>> what can be done to fix it. Having looked in my final target filesystem
>>> there are no links to the volatiles in /var/voltatile/* to /*, should
>>> there be? The base-files packages looks like it should do it but
>>> obviously something is going wrong.
>>>
>>>     for d in ${volatiles}; do
>>>       ln -sf volatile/$d ${D}${localstatedir}/$d
>>>     done
>> We're using base-files bbappend to create it and also replacing few
>> symlinks to volatile with real directories (not mandatory for systemd
>> iirc, but useful in some cases).
>>
>> https://github.com/shr-distribution/meta-smartphone/commit/24161eed3c185867b2fd91aab6532f370d327cdd 
>>
>>
>
> Ok, manually adding /run to 775dirs in a base-files append fixed this 
> for me. I still don't understand why this should be needed as an 
> addition though...
>
I get this error booting hdddirect/vmdk image (no initrd) but not when 
booting hddimg (uses initrd).

Regards,
Jonathan