[Buildroot] [PATCH 1/1] systemd: ensure tmpfiles.d/legacy.conf is installed

[Arnout Vandecappelle]

On 08/01/2022 22:17, Norbert Lange wrote:
> Am Sa., 8. Jan. 2022 um 21:40 Uhr schrieb Arnout Vandecappelle <arnout at mind.be>:
>>
>>
>> On 08/01/2022 20:12, Arnout Vandecappelle wrote:
>>>
>>>
>>> On 25/08/2020 02:02, Joseph Kogut wrote:
>>>> Systemd doesn't install tmpfiles.d/legacy.conf when sysv compatiblity
>>>> isn't enabled. This config sets up /var/lock, which many programs such
>>>> as uboot's fw_printenv/setenv still depend on by default.
>>>>
>>>> Signed-off-by: Joseph Kogut <joseph.kogut at gmail.com>
>>>
>>>   After all the discussion, I did finally apply to master, thanks.
>>
>>    And I ended up reverting it again - legacy.conf is now legacy.conf.in and it
>> needs to be preprocessed, but that is only done if sysv-compat is enabled.
>>
>>    So if we want this, our only option is to enable sysv-compat (which is
>> probably something we should do anyway).
> 
> Why the only option? you should just ship your own legacy.conf, it wont change.

  I meant: if we want to use the legacy.conf from upstream. But you're right 
it's not the only option, we could also manually sed out stuff from the .in file.


> Adding sysv compatibility, which is alot more than just the mkdir and
> symlink, would mean adding alot baggage.

  Ack.

> Baggage that wont even work as Yann spake thusly [1]
> 
> a tmpfile.conf with those 3 lines would be enough:
> d /run/lock 0755 root root -
> L /var/lock - - - - ../run/lock
> d /run/lock/subsys 0755 root root -

  All right, I hope I remember this by the time a see the patch :-)

> 
> Norbert.
> 
> PS. I am too lazy to google everything up, but I believe I brought up
> this very topic before.

  I'm also too lazy to google it.

  Regards,
  Arnout

> 
> [1] - https://lists.buildroot.org/pipermail/buildroot/2020-July/287275.html
>