From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chen Qi <Qi.Chen@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] systemd: add back alternatives for init utitilies
Date: Sat, 20 Oct 2018 22:37:11 +0100 [thread overview]
Message-ID: <2980ba34e7eb66ad6ad22d5cd85b12a9bb7e30b2.camel@linuxfoundation.org> (raw)
In-Reply-To: <aa81e6d3c24822a91432cac5af20378a65301254.1539926193.git.Qi.Chen@windriver.com>
On Fri, 2018-10-19 at 13:19 +0800, Chen Qi wrote:
> Add back alternatives for init utilities to avoid regression.
>
> These alternatives were removed when upgradeing systemd to 239.
> They were removed out of the logic that init utitilies should be
> bound to init manager. However, it turned out that two use cases
> were not covered.
>
> 1) initramfs using commands like 'reboot' from busybox.
> 2) Users use customized busybox defconfig which enables init
> utilities.
>
> The first use case caused a regression bug in yocto.
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12914
> Patches were sent to fix the reboot problem.
>
> But this is not enough. As we may have the second use case. In such
> situation, users will find themselves having regression error when
> using 'busybox + systemd' (and busybox is installed after systemd,
> overriding the systemd symlinks).
>
> So in order to avoid regression, add back these alternatives.
>
> Signed-off-by
There is something odd going on which this change since it triggers:
https://autobuilder.yoctoproject.org/typhoon/#/builders/35/builds/95/steps/7/logs/step7c
I've isolated it to this change having initially thought it was Mark's
systemd change...
Cheers,
Richard
next prev parent reply other threads:[~2018-10-20 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 5:19 [PATCH 0/1] systemd: add back alternatives for init utitilies Chen Qi
2018-10-19 5:19 ` [PATCH 1/1] " Chen Qi
2018-10-20 21:37 ` Richard Purdie [this message]
2018-10-22 7:01 ` ChenQi
2018-10-22 7:20 ` Hongzhi, Song
-- strict thread matches above, loose matches on Subject: below --
2018-10-22 7:03 [PATCH V2 0/1] " Chen Qi
2018-10-22 7:03 ` [PATCH 1/1] " Chen Qi
2018-10-23 21:48 ` Richard Purdie
2018-10-24 6:16 ` ChenQi
2018-10-25 23:02 ` richard.purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2980ba34e7eb66ad6ad22d5cd85b12a9bb7e30b2.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox