From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Young Subject: Re: rdshell and rdbreak Date: Thu, 29 Sep 2011 17:20:57 +0800 Message-ID: <4E843879.9010000@redhat.com> References: <4E8413A6.2090804@redhat.com> <4E842B3C.4080707@redhat.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E842B3C.4080707-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Sender: initramfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Harald Hoyer Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On 09/29/2011 04:24 PM, Harald Hoyer wrote: > 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" ?? Thanks for comment, harald I think it's still not so convenience to use two params for this issue, and 'cmdline' also looks a little confuse for me. But it's up to you so long as we can managed to have this feature. -- Thanks Dave