Am 05.01.23 um 15:57 schrieb Richard Purdie:
On Thu, 2023-01-05 at 15:23 +0100, Michael Opdenacker wrote: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?We should really fix poky so this works correctly. I just have a memory of trying to fix it and it not being as straightforward it first appears. I'd then have got distracted by the next problem :/
As far as I am concerned, I tried to set INIT_MANAGER with "?=" in poky.conf and the set INIT_MANAGER = "systemd" in local.conf and the resulting system was booting fine. Shall we make the change in master and see if autobuilders catch any issue? Unless your remember was the complexity was about.
Or shall I file a bug so that one of us addresses this when (s)he has time? Thanks for your help on this! Cheers Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#175537): https://lists.openembedded.org/g/openembedded-core/message/175537 Mute This Topic: https://lists.openembedded.org/mt/92210454/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
