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 v2] allow ifup bring up network manually even without netroot
Date: Fri, 13 Jan 2012 16:58:42 +0800 [thread overview]
Message-ID: <4F0FF242.506@gmail.com> (raw)
In-Reply-To: <4F0E4055.90903-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 01/12/2012 10:07 AM, Dave Young wrote:
>>>> If we need to invoke `ifup` by
>>>> ourselves, then we also need to determine which NIC we should bring
>>>> up, this will make kdump code larger.
>>>>
>>>> So, I hope, we can have some kernel cmdline (like ip=...) to tell
>>>> dracut which NIC we want to bring up in the second kernel, provided by
>>>> either ssh-client module or nfs module.
>>>
>>>
>>> If we need to pass the nic name to cmdline then we still need to
>>> determine which one should be use.
>>
>>
>> Sure, but this will go to ssh-client or nfs module, not kdump.
>
>
> ssh-client does not pass any cmdline, instead the scripts of call dracut
> to generate initrd do this. In case of kdump it's the kdump init scripts
> or simplified mkdumprd, so we could not skip this step.
Well, I still think ssh-client or nfs module should handle the network,
not kdump's mkdumprd, like lvm module for lvm.* cmdline.
But anyway, I will take this patch to my kdump tree.
Thanks.
prev parent reply other threads:[~2012-01-13 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 8:38 [PATCH v2] allow ifup bring up network manually even without netroot Dave Young
2012-01-10 15:41 ` Cong Wang
2012-01-11 2:05 ` Dave Young
[not found] ` <4F0CEE74.6020102-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-11 2:08 ` Dave Young
2012-01-11 9:48 ` Cong Wang
[not found] ` <4F0D5ADE.4020800-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-12 2:07 ` Dave Young
[not found] ` <4F0E4055.90903-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-13 8:58 ` Cong Wang [this message]
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=4F0FF242.506@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