Skip to contentSkip to conversation

Migration dunfell to kirkstone , init manager issue

OE-core Frédéric Martinsons 1 participant 2 messages Nov 18, 2023 – Nov 19, 2023 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

I saw in log.do_rootfs that update_alternatives task links /sbin/init to busybox.
I saw also that the default config (init.cfg) have CONFIG_INIT=y (in openembedded-core layer), dunfell also had it too but, in the end, it was not taken into account.

I'll look further about busybox config and update-alternatives class unless someone here have a clue about what is going on.

Quoted 43 lines · Frederic Martinsons via lists.openembedded.org

Hello,

I recently started upgrading my system from dunfell to kirkstone and I started with a basic (but custom nonetheless) qemu image that I used in dunfell (before starting machine/distro specific ops).

After several corrections , many thanks by the way for the various convert scripts !, I managed to get my qemu image built on kirkstone.

But when I didn't manage to boot it correctly (I used qemu-system-x86-64 of my host) and every second on prompt I got these messages

process '-/bin/sh' (pid 143) exited. Scheduling for restart. process '-/bin/sh' (pid 144) exited. Scheduling for restart. process '-/bin/sh' (pid 145) exited. Scheduling for restart. can't open /dev/tty2: No such file or directory can't open /dev/tty3: No such file or directory can't open /dev/tty4: No such file or directory

I looked into it more and found that the init system is set to busybox (/sbin/init point to /bin/busybox.nosuid).
My system needs systemd as init manager and I verify that I have set INIT_MANAGER="systemd" in my configuration (I even perform a bitbake -e to check that this is not overridden).

Can someone please tell me where to look (which log file, or some oe tools that I can use) to find why systemd is not used as the init manager ?

Thanks.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#190853):
https://lists.openembedded.org/g/openembedded-core/message/190853
Mute This Topic: https://lists.openembedded.org/mt/102649719/6213388
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#2 lore raw
Quoted 9 lines · Frédéric Martinsons

I saw in log.do_rootfs that update_alternatives task links /sbin/init to busybox.
I saw also that the default config (init.cfg) have CONFIG_INIT=y (in openembedded-core layer), dunfell also had it too but, in the end, it was not taken into account.

I'll look further about busybox config and update-alternatives class unless someone here have a clue about what is going on.

In the end, I managed to get back systemd as init system by adding an append to busybox and set explictely "CONFIG_INIT is not set" I gave up on understanding this change of behavior towards how it was done on dunfell (simply set INIT_MANAGER="systemd")

Quoted 47 lines
Quoted 43 lines · Frederic Martinsons via lists.openembedded.org

Hello,

I recently started upgrading my system from dunfell to kirkstone and I started with a basic (but custom nonetheless) qemu image that I used in dunfell (before starting machine/distro specific ops).

After several corrections , many thanks by the way for the various convert scripts !, I managed to get my qemu image built on kirkstone.

But when I didn't manage to boot it correctly (I used qemu-system-x86-64 of my host) and every second on prompt I got these messages

process '-/bin/sh' (pid 143) exited. Scheduling for restart. process '-/bin/sh' (pid 144) exited. Scheduling for restart. process '-/bin/sh' (pid 145) exited. Scheduling for restart. can't open /dev/tty2: No such file or directory can't open /dev/tty3: No such file or directory can't open /dev/tty4: No such file or directory

I looked into it more and found that the init system is set to busybox (/sbin/init point to /bin/busybox.nosuid).
My system needs systemd as init manager and I verify that I have set INIT_MANAGER="systemd" in my configuration (I even perform a bitbake -e to check that this is not overridden).

Can someone please tell me where to look (which log file, or some oe tools that I can use) to find why systemd is not used as the init manager ?

Thanks.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#190853):
https://lists.openembedded.org/g/openembedded-core/message/190853
Mute This Topic: https://lists.openembedded.org/mt/102649719/6213388
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-