From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] runqemu-internel: add 'debugshell' as a default kernel option
Date: Wed, 9 Jan 2013 10:27:35 +0800 [thread overview]
Message-ID: <50ECD597.9090403@windriver.com> (raw)
In-Reply-To: <239f0850af3e3f0ed83263e4306420f4f0684088.1357615514.git.Qi.Chen@windriver.com>
Sorry about the typo in subject.
I'll fix the typo and send out this patch again.
Chen Qi
On 01/08/2013 05:06 PM, Qi.Chen@windriver.com wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> Add 'debugshell' as a default kernel option for ramfs booting.
>
> If rootfs.img cannot be found under /media, init-live.sh loops
> forever without showing any information. Silently looping forever
> and blocking users is inappropriate.
>
> Now that the 'debugshell' feature has been implemented in init-live.sh,
> It's reasonable to add it to the kernel option when booting a ramfs-based
> image. In this way, the system doesn't loop forever and instead drops
> to a shell after a default timeout (30 seconds).
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> scripts/runqemu-internal | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
> index a11220d..9d570ed 100755
> --- a/scripts/runqemu-internal
> +++ b/scripts/runqemu-internal
> @@ -472,7 +472,7 @@ fi
>
> if [ "x$RAMFS" = "xtrue" ]; then
> QEMUOPTIONS="-initrd $ROOTFS -nographic"
> - KERNCMDLINE="root=/dev/ram0"
> + KERNCMDLINE="root=/dev/ram0 debugshell"
> fi
>
> if [ "x$QEMUOPTIONS" = "x" ]; then
prev parent reply other threads:[~2013-01-09 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 9:06 [PATCH 0/1] runqemu-internal: add 'debugshell' as a default kernel option Qi.Chen
2013-01-08 9:06 ` [PATCH 1/1] runqemu-internel: " Qi.Chen
2013-01-09 2:27 ` ChenQi [this message]
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=50ECD597.9090403@windriver.com \
--to=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