All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: rdshell and rdbreak
Date: Thu, 29 Sep 2011 10:24:28 +0200	[thread overview]
Message-ID: <4E842B3C.4080707@redhat.com> (raw)
In-Reply-To: <4E8413A6.2090804-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 09/29/2011 08:43 AM, Dave Young wrote:
> Hi,
>
> For kernel developers sometimes boot-test need a minimal initrd, so just
> drop into a shell is a nice feature.
>
> The first impression of param 'rdshell' to me is it will drop me into a
> shell, but It doesn't. It drop into shell only when initramfs fails.
>
> The rdbreak is more near what I want, but it still fails when no root
> args set in cmdline.
>
> IMO initrd can provide such options at least: dropping into shell
> without mount rootfs, user can mount by himself or do other things.
>
> Thus, if it make sense how about add a:
> rdbreak=force
>
> OTOH, rdshell can be merged into rdbreak as:
> rdbreak=fail
>
> Any comments about this?

what about "rdshell rdbreak=cmdline" or
in new syntax "rd.shell=1 rd.break=cmdline" ??

  parent reply	other threads:[~2011-09-29  8:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29  6:43 rdshell and rdbreak Dave Young
     [not found] ` <4E8413A6.2090804-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-29  8:24   ` Harald Hoyer [this message]
     [not found]     ` <4E842B3C.4080707-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-29  9:20       ` Dave Young
     [not found]         ` <4E843879.9010000-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-29  9:42           ` Dave Young
     [not found]             ` <4E843D6B.9040302-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-29  9:44               ` 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=4E842B3C.4080707@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dyoung-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.