mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH v2 0/2] add parameter continue_on_fail
Date: Mon, 18 Feb 2013 14:21:41 +0800	[thread overview]
Message-ID: <cover.1361167889.git.bhe@redhat.com> (raw)

v1->v2:
    Discard previous implementation, take a direct and simpler
    method.

By adding pamameter 'continue_on_fail=initqueue|mount_root',
user can decide if continue after these points timeout. And
can extend to other delay or loop point later if needed.

Baoquan He (2):
  Add parameter continue_on_fail to make dracut continue after
    initqueue timeout
  Continue when mount rootfs failed by specifing
    'continue_on_fail=mount_root'

 dracut.cmdline.7.asc                    |    3 +++
 modules.d/98systemd/dracut-initqueue.sh |   10 ++++++++--
 2 files changed, 11 insertions(+), 2 deletions(-)

             reply	other threads:[~2013-02-18  6:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18  6:21 Baoquan He [this message]
     [not found] ` <cover.1361167889.git.bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-02-18  6:21   ` [PATCH v2 1/2] Add parameter continue_on_fail to make dracut continue after initqueue timeout Baoquan He
2013-02-18  6:21   ` [PATCH v2 2/2] Continue when mount rootfs failed by specifing 'continue_on_fail=mount_root' Baoquan He
2013-02-18 10:29   ` [PATCH v2 0/2] add parameter continue_on_fail Harald Hoyer
     [not found]     ` <51220277.1010507-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-02-19  5:03       ` Baoquan
     [not found]         ` <51230787.7090706-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-02-19  8:02           ` Dave Young
2013-02-28  3:38       ` Dave Young

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=cover.1361167889.git.bhe@redhat.com \
    --to=bhe-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@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