From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 20 Jul 2017 09:32:28 +0200 Subject: [Buildroot] [PATCH 00/20] system: properly handle systemd as init system In-Reply-To: References: <20170719225332.560a9a06@windsurf> Message-ID: <20170720093228.19139327@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Wed, 19 Jul 2017 15:17:21 -0700, Andrey Yurovsky wrote: > > 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. Awesome, thanks. > > 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. Can you reproduce the problem *without* the patches ? > /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. Thanks a lot! BTW, for these bugs, if there is something easy we can add to the testing infrastructure to make sure it keeps working, it would be nice! Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com