From: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Change the implementation of action_on_fail
Date: Thu, 1 Aug 2013 09:48:23 -0400 [thread overview]
Message-ID: <20130801134823.GD15235@redhat.com> (raw)
In-Reply-To: <73cc07330929ba4b226f2a0623a5459cd42932b9.1374574542.git.bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Tue, Jul 23, 2013 at 06:16:00PM +0800, Baoquan He wrote:
[..]
> diff --git a/modules.d/99base/dracut-lib.sh b/modules.d/99base/dracut-lib.sh
> index 8eeebf3..2a3d831 100755
> --- a/modules.d/99base/dracut-lib.sh
> +++ b/modules.d/99base/dracut-lib.sh
> @@ -1003,24 +1003,16 @@ emergency_shell()
>
> action_on_fail()
> {
> - local _action=$(getarg rd.action_on_fail= -d action_on_fail=)
> - case "$_action" in
> - continue)
> - [ "$1" = "-n" ] && shift 2
> - [ "$1" = "--shutdown" ] && shift 2
> - warn "$*"
> - warn "Not dropping to emergency shell, because 'action_on_fail=continue' was set on the kernel command line."
> - return 0
> - ;;
> - shell)
> - emergency_shell $@
> - return 1
> - ;;
> - *)
> - emergency_shell $@
> - return 1
> - ;;
> - esac
> + if [ -f "$initdir/lib/dracut/no-emergency-shell" ]; then
> + [ "$1" = "-n" ] && shift 2
> + [ "$1" = "--shutdown" ] && shift 2
> + warn "$*"
> + warn "Not dropping to emergency shell, because 'action_on_fail=continue' was set on the kernel command line."
Bao,
Ok, so you have completely removed the parameter rd.action_on_fail. I got
confused with above message "'action_on_fail=continue' was set on the
kernel command line".
I see that it has been fixed in the commit and replaced with following
message.
"Not dropping to emergency shell, because $initdir/lib/dracut/no-emergency-shell exists."
This makes sense now.
Thanks
Vivek
next prev parent reply other threads:[~2013-08-01 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 10:16 [PATCH] Change the implementation of action_on_fail Baoquan He
[not found] ` <73cc07330929ba4b226f2a0623a5459cd42932b9.1374574542.git.bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-23 10:25 ` Baoquan
2013-07-31 14:07 ` Harald Hoyer
[not found] ` <51F91A14.4020601-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-31 14:20 ` Vivek Goyal
[not found] ` <20130731142050.GG31151-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-31 14:25 ` Harald Hoyer
[not found] ` <51F91E75.3070102-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-31 14:29 ` Vivek Goyal
[not found] ` <20130731142905.GH31151-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-31 14:31 ` Harald Hoyer
[not found] ` <51F91FAC.50706-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-08-01 14:24 ` Baoquan He
[not found] ` <20130801142445.GB8230-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-08-01 14:54 ` Vivek Goyal
2013-08-01 14:54 ` WANG Chao
2013-07-31 14:27 ` Vivek Goyal
2013-08-01 13:48 ` Vivek Goyal [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-22 11:32 Baoquan He
[not found] ` <8a7ac3492f63fd2a5fa7ee57d9b9e7c8c2dd305c.1374492675.git.bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-23 9:53 ` Baoquan
2013-07-23 10:14 ` Baoquan
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=20130801134823.GD15235@redhat.com \
--to=vgoyal-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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