From: Adrian Freihofer <adrian.freihofer@gmail.com>
To: gavrosc@yahoo.com, openembedded-core@lists.openembedded.org
Cc: Yoann Congal <yoann.congal@smile.fr>,
Randy MacLeod <randy.macleod@windriver.com>,
Ross Burton <ross.burton@arm.com>, jbk <jbk@mm-software.com>
Subject: Re: [OE-core] [PATCH] initramfs-framework: remove hard dependency with busybox
Date: Sat, 29 Mar 2025 14:45:13 +0100 [thread overview]
Message-ID: <19c7cc6289d7aab486e74ac50bdbf17a22e86363.camel@gmail.com> (raw)
In-Reply-To: <20250328180456.90413-1-gavrosc@yahoo.com>
Hi Christos
Since the -c has been around for a very long time, I assume that there
are many users who use it with busybox. Using it with core-utils will
probably remain the special use case.
The proposed fix raises the question of why the -c was introduced at
some point. If your fix also works for busybox, was the -c always
redundant? Or has something changed in the meantime?
Please also address the busybox users' point of view in the commit
message and summarize how this was tested with busybox in particular.
Thank you.
Adrian
On Fri, 2025-03-28 at 19:04 +0100, Christos Gavros via
lists.openembedded.org wrote:
> In 'finish'script the Switch_root command with option -c is busybox
> specific.
> When package-core-base-utils is selected the boot is breaking.
> Remove -c option to make it compatible with both providers
> Fixes [YOCTO #15716]
>
> CC: Yoann Congal <yoann.congal@smile.fr>
> CC: Randy MacLeod <randy.macleod@windriver.com>
> CC: Ross Burton <ross.burton@arm.com>
> CC: jbk <jbk@mm-software.com>
> Signed-off-by: Christos Gavros <gavrosc@yahoo.com>
> ---
> meta/recipes-core/initrdscripts/initramfs-framework/finish | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/initrdscripts/initramfs-
> framework/finish b/meta/recipes-core/initrdscripts/initramfs-
> framework/finish
> index ac0de9f996..716c2f44af 100755
> --- a/meta/recipes-core/initrdscripts/initramfs-framework/finish
> +++ b/meta/recipes-core/initrdscripts/initramfs-framework/finish
> @@ -41,7 +41,7 @@ finish_run() {
> mount --move /sys $ROOTFS_DIR/sys
>
> cd $ROOTFS_DIR
> - exec switch_root -c /dev/console $ROOTFS_DIR
> ${bootparam_init:-/sbin/init}
> + exec switch_root $ROOTFS_DIR ${bootparam_init:-
> /sbin/init}
> else
> debug "No rootfs has been set"
> fi
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#213861):
> https://lists.openembedded.org/g/openembedded-core/message/213861
> Mute This Topic: https://lists.openembedded.org/mt/111959232/4454582
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe:
> https://lists.openembedded.org/g/openembedded-core/unsub [
> adrian.freihofer@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2025-03-29 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250328180456.90413-1-gavrosc.ref@yahoo.com>
2025-03-28 18:04 ` [PATCH] initramfs-framework: remove hard dependency with busybox Christos Gavros
2025-03-29 13:45 ` Adrian Freihofer [this message]
2025-03-29 16:01 ` Christos Gavros
2025-03-29 16:29 ` [OE-core] " Khem Raj
2025-04-10 21:27 ` Adrian Freihofer
2025-04-11 9:40 ` 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=19c7cc6289d7aab486e74ac50bdbf17a22e86363.camel@gmail.com \
--to=adrian.freihofer@gmail.com \
--cc=gavrosc@yahoo.com \
--cc=jbk@mm-software.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
--cc=ross.burton@arm.com \
--cc=yoann.congal@smile.fr \
/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