mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Steffen Maier <maier-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: New rd.* namespace for dracut-008
Date: Thu, 28 Oct 2010 19:05:25 +0200	[thread overview]
Message-ID: <4CC9AD55.7010104@redhat.com> (raw)
In-Reply-To: <4CC9AB0E.2040604-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>

On 10/28/2010 06:55 PM, Steffen Maier wrote:
> Harald, thanks for the update.
> Just one quick question below.
>
> On 10/28/2010 05:17 PM, Harald Hoyer wrote:
>> I cleaned up the kernel command line parameters and moved them to the
>> rd.* namespace. The deprecated options are supported until dracut-010
>> and will be removed afterwards.
>>
>> Here is a list of options, which were used in dracut prior to
>> version 008, and their new replacement.
>
>> rd_CCW
>> rd.ccw
>
>> rd_DASD_MOD
>> rd.dasd_mod.dasd
>
> Is this a typo?
> I'm wondering why the new one is not just "rd.dasd_mod".
> Having a .dasd suffix is not necessary and users might mix it up with rd.dasd
> which has both syntax and semamtics differently.

because it's the "dasd" parameter of the dasd_mod module

one could specify it directly on the kernel command with "dasd_mod.dasd=", which 
would be honored by the module itsself. So I just added "rd." to indicate the 
sole use for the initramfs.

>
>> rd_DASD
>> rd.dasd
>
>> rd_NO_ZFCPCONF
>> rd.zfcp.conf=0
>>
>> rd_ZFCP
>> rd.zfcp
>
> Steffen
>
> Linux on System z Development
>
> IBM Deutschland Research & Development GmbH
> Vorsitzender des Aufsichtsrats: Martin Jetter
> Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
>

  parent reply	other threads:[~2010-10-28 17:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 15:17 New rd.* namespace for dracut-008 Harald Hoyer
     [not found] ` <4CC99414.5060607-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-10-28 15:46   ` maximilian attems
     [not found]     ` <20101028154604.GA32323-VJknIhvjf2Ov8OlOgJ4AIV6hYfS7NtTn@public.gmane.org>
2010-10-28 15:53       ` Harald Hoyer
2010-10-28 16:55   ` Steffen Maier
     [not found]     ` <4CC9AB0E.2040604-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2010-10-28 17:05       ` Harald Hoyer [this message]
     [not found]         ` <4CC9AD55.7010104-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-10-28 17:40           ` Bill Nottingham
     [not found]             ` <20101028174048.GA2367-Zdt1ptygihhQcNjhGXsBABcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2010-10-29  8:18               ` Harald Hoyer
2010-10-28 17:41   ` Bill Nottingham
     [not found]     ` <20101028174147.GB2367-Zdt1ptygihhQcNjhGXsBABcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2010-10-29  8:17       ` Harald Hoyer

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=4CC9AD55.7010104@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=maier-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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