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:31:53 +0800	[thread overview]
Message-ID: <4F266389.70303@gmail.com> (raw)
In-Reply-To: <4F266004.5080501-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 01/30/2012 05:16 PM, Dave Young wrote:
>
> How to say...
> There's many different configs for network like:
> 1. ip={dhcp|on|any|dhcp6|auto6|ibft}
> 2. ip=<interface>:{dhcp|on|any|dhcp6|auto6}
> 3. ip=<client-IP>:[<server-id>
> ]:<gateway-IP>:<netmask>:<client_hostname>:<interface>:{none|off}
> 4. ifname=
> 5. bootdev=
> 6. root=nfs:[snip]
>
> They are all possibly be used, IHMO they are not good options for this
> patch using. For example there's no NIC specified in 1 and 3, we will
> still have to bring up the default


Kdump module can make sure that at least one NIC will be specified, if 
there is ip=.

>
> Also this is a general feature, maybe it will be used by users other
> than kdump. For kdump I think we can use proper ip= plus rd.neednet=1
>

Why? If we can re-use ip=, it will imply rd.neednet=1, so again, 
rd.neednet is not needed.

Thanks.

  parent reply	other threads:[~2012-01-30  9:31 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
     [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 [this message]
     [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=4F266389.70303@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