mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] auto setup network without netroot
Date: Mon, 30 Jan 2012 17:03:23 +0800	[thread overview]
Message-ID: <4F265CDB.7070204@gmail.com> (raw)
In-Reply-To: <4F265C01.4010701-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 01/30/2012 04:59 PM, Dave Young wrote:
> On 01/30/2012 04:51 PM, Cong Wang wrote:
>
>> On 01/30/2012 04:51 PM, Dave Young wrote:
>>>
>>> We will also setup network when rd.neednet=1 in case no special ip=
>>> provided for convenience.
>>>
>>
>> With rd.neednet=1 but without ip=, how can you know which nic we need to
>> bring up?
>
>
> current behavior of net-genrule.sh is below:
>
> # Default: We don't know the interface to use, handle all
>
> It will be ok and convenient at least when we have only one nic

So, rd.neednet=1 will bring up all when there is no ip=, what kdump 
needs is a cmdline that tells dracut to bring up only the ones we need.

You still don't tell why re-using ip= doesn't work. So far, I think ip= 
can be re-used for kdump case, and is better than your rd.neeednet=1.

  parent reply	other threads:[~2012-01-30  9:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30  6:43 [PATCH] auto setup network without netroot Dave Young
2012-01-30  8:33 ` Cong Wang
2012-01-30  8:51   ` Dave Young
     [not found]     ` <4F265A0B.1000402-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-30  8:51       ` Cong Wang
     [not found]         ` <4F265A22.2090407-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-30  8:59           ` Dave Young
     [not found]             ` <4F265C01.4010701-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-30  9:03               ` Cong Wang [this message]
     [not found]                 ` <4F265CDB.7070204-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-30  9:16                   ` Dave Young
     [not found]                     ` <4F266004.5080501-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-30  9:31                       ` Cong Wang
     [not found]                         ` <4F266389.70303-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-30  9:49                           ` Dave Young
     [not found]                             ` <4F2667A4.4080203-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-30 10:03                               ` Cong Wang
     [not found]                                 ` <4F266AEE.703-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-31  1:42                                   ` 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=4F265CDB.7070204@gmail.com \
    --to=xiyou.wangcong-re5jqeeqqe8avxtiumwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox