From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>,
Khem Raj <raj.khem@gmail.com>,
"Robert P. J. Day" <rpjday@crashcourse.ca>,
YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [OE-core] is "poky" distro defined to use "sysvinit" as INIT_MANAGER?
Date: Thu, 5 Jan 2023 15:23:14 +0100 [thread overview]
Message-ID: <b725dbd2-3825-1eb7-3f71-a19a17c2ef7f@bootlin.com> (raw)
In-Reply-To: <1736D38C7177CA6A.6604@lists.openembedded.org>
Am 03.01.23 um 15:41 schrieb Michael Opdenacker via lists.openembedded.org:
> Hello Richard,
>
> Trying to improve the documentation about the selection of the init
> system, I'm jumping back to this old conversation, following a change
> that you made (https://lists.yoctoproject.org/g/poky/message/12760).
>
> Am 06.07.22 um 18:40 schrieb Khem Raj:
>> On Wed, Jul 6, 2022 at 12:38 PM Robert P. J. Day
>> <rpjday@crashcourse.ca> wrote:
>>>
>>> not sure why i never noticed this before, but i started a new
>>> project from the poky layer (not OE), and realized that poky.conf
>>> explicitly sets:
>>>
>>> INIT_MANAGER = "sysvinit"
>>>
>>> which can't be overridden in my local.conf. if i want systemd, i guess
>>> i can initialize my project from the OE layer, and i also notice that
>>> i could use poky-altcfg.conf.
>>>
>>> but is there a reason that the default poky-based project fixes
>>> INIT_MANAGER to "sysvinit". perhaps just for simplicity?
>>>
>> poky defaults to sysvinit.
>> poky has poky-alt distro fi you want to use say systemd
>
> But why not setting INIT_MANAGER with "?=" instead of "=" in poky.conf?
>
> This way, we could just override INIT_MANAGER from local.conf.
>
> I checked that the generated system works. This would make things
> easier to document, unless I'm missing other reasons.
Richard told me on IRC that, from memory, this was set because of
interference poky-altcfg (if I understood correctly).
I understand one recommended way to have systemd instead of sysvinit in
Poky is to use "poky-altcfg" instead of "poky" as distro.
Similarly, I guess I should use "poky-tiny" if I want to use
"mdev-busybox" as INIT_MANAGER.
Then, I guess I'll document something like this:
* With the OpenEmbedded build system, you can choose your init system
by setting INIT_MANAGER to "sysvinit", "systemd", "busybox-mdev" or
"none"
* BUT if you're using Poky, that won't work, so your options will be
to use either "poky" (sysvinit), "poky-altcfg" (systemd) or
"poky-tiny" (mdev-busybox).
Does this sound like the right way to document this?
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2023-01-05 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2893205d-57e1-e63e-5c12-c57c7bbcb924@crashcourse.ca>
[not found] ` <CAMKF1spKw-X-JTvdicfBBNNGk93EPL=gqD3jixvJkb7YfT1P0g@mail.gmail.com>
[not found] ` <1736D38C7177CA6A.6604@lists.openembedded.org>
2023-01-05 14:23 ` Michael Opdenacker [this message]
2023-01-05 14:57 ` [OE-core] is "poky" distro defined to use "sysvinit" as INIT_MANAGER? Richard Purdie
2023-01-05 15:02 ` Michael Opdenacker
2023-01-05 15:09 ` [docs] " Alexander Kanavin
2023-01-05 21:46 ` Peter Kjellerstedt
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=b725dbd2-3825-1eb7-3f71-a19a17c2ef7f@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=rpjday@crashcourse.ca \
/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