[Buildroot] [PATCH 00/20] system: properly handle systemd as init system

Andrey Yurovsky yurovsky at gmail.com
Wed Jul 19 22:17:21 UTC 2017


On Wed, Jul 19, 2017 at 1:53 PM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> Hello,
>
> On Wed, 19 Jul 2017 13:14:58 -0700, Andrey Yurovsky wrote:
>
>> For what it's worth,
>>
>> Tested-by: Andrey Yurovsky <yurovsky at gmail.com>
>>
>> using some in-house configs (armv5 and armv7) with and without
>> systemd-networkd, verified journald functionality and the state of
>> /var and so on.
>
> Thanks a lot for testing, very useful to get some feedback!
>
> Can you confirm that it fixes the journald issue reported in bug
> https://bugs.busybox.net/show_bug.cgi?id=7892 ?

It does.

> Also, it would be useful if someone interested in systemd could look at
> bugs https://bugs.busybox.net/show_bug.cgi?id=9881 and

I did an ARMv7 build with networkd+resolvd and couldn't reproduce the
described problem with these patches applied. /etc/resolv.conf points
to ../tmp/resolv.conf which in turn is properly populated and names do
resolve. systemd-hostnamed is acting like it does on Fedora (for what
it's worth), I'm still learning about how to test it properly (that
is, I just have a static hostname at the moment).

> https://bugs.busybox.net/show_bug.cgi?id=9926.

Ok, I'll do a clean rebuild without networkd and with NetworkManager.

> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com



More information about the buildroot mailing list