[OE-core] [PATCH 1/2] systemd: upgrade to 239

[Ricardo Salveti]

On Thu, Jul 26, 2018 at 2:50 AM, ChenQi <Qi.Chen at windriver.com> wrote:
> On 07/26/2018 07:05 AM, Ricardo Salveti wrote:
>> I noticed that reboot stopped working locally as I had busybox
>> installed together with systemd, and the busybox version ended up
>> being used as it was provided via update-alternatives.
>>
>> Looking for possible similar broken links, I found that
>> update-alternatives ended up pointing reboot, halt and poweroff to the
>> busybox binary instead of systemctl. Should we revert the changes and
>> bring back update-alternatives for them?
>
> I think the correct direction to fix this problem is to make busybox only
> provide init utilities (reboot, halt, etc) when init manager is set to
> busybox.
>
> We current have in busybox recipe's SRC_URI:
>            ${@["",
> "file://init.cfg"][(d.getVar('VIRTUAL-RUNTIME_init_manager') == 'busybox')]}
> \
>
> I think the init utilities should be moved to init.cfg.
>
> Please check my logic to see if you can agree with it.
> We have two facts here.
> 1. Init utilities (reboot, halt, etc.) are tightly bond to the specific
> implementation of PID 1.
> 2. We only allow one PID 1 in our image. (VIRTUAL-RUNTIME_init_manager).
> So we can conclude from the above two facts that it does not make much sense
> to have multiple providers of init utilities while we only allow one PID 1
> provider on image.

Seems correct to move the init utilities to init.cfg even without the
update-alternatives change then.

> After all, we are using update-*alternatives*, things that this mechanism
> manages are supposed to generally serve as alternatives to each other.
>
> Best Regards,
> Chen Qi

Cheers,
-- 
Ricardo Salveti de Araujo