Skip to content

system: properly handle systemd as init system

Thomas Petazzoni buildroot 1 version In review

Get series with b4
b4 am 20170720093228.19139327@windsurf

Versions newest first

  1. v1 Latest12 of 20 patches 1 replyIn review

12 of 20 patches are in this archive. The cover letter announces 20.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
2/20core/pkg-generic: add variable to skip skeleton dependency+0 -00 replies
3/20package/skeleton: add macro to rsync skeleton directory+0 -00 replies
4/20package/skeleton: make SKELETON_LIB_SYMLINK a macro+0 -01 reply
4/20package/skeleton: make SKELETON_LIB_SYMLINK a macro+0 -00 replies
4/20package/skeleton: make SKELETON_LIB_SYMLINK a macro+0 -01 reply
6/20system: move setting getty to the corresponding init systems+0 -01 reply
6/20system: move setting getty to the corresponding init systems+0 -00 replies
7/20system: move remounting / to the corresponding init systems+0 -00 replies
12/20package/skeleton: split out into skeleton-common+0 -01 reply
20/20support/testing: add runtime testing for init systems+0 -00 replies
20/20support/testing: add runtime testing for init systems+0 -01 reply
20/20support/testing: add runtime testing for init systems+0 -08 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

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

Hello,

Quoted 6 lines · Andrey Yurovsky
Quoted 4 lines

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.

Quoted 5 lines
Quoted 2 lines

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 ?

Quoted 9 lines

/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).

Quoted 1 line

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

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com