mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Cong Wang <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] allow ifup bring up network manually even without netroot
Date: Wed, 11 Jan 2012 10:08:20 +0800	[thread overview]
Message-ID: <4F0CEF14.5030206@redhat.com> (raw)
In-Reply-To: <4F0CEE74.6020102-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 01/11/2012 10:05 AM, Dave Young wrote:

> Hi, I have some additional comments
> 
> On 01/10/2012 11:41 PM, Cong Wang wrote:
> 
>> On Fri, 30 Dec 2011 at 08:38 GMT, Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>>> For kdump we need scp vmcore to remote machine, the nic to be used is
>>> not limited to netroot one. we need a feature for manually bringing up
>>>  network interface. Also it is useful for emergency shell with
>>> ssh-client for recovery or test purpose
>>>
>>> I implement this by adding one argument to ifup script, user can use
>>> `/sbin/ifup eth0 -m` to bring up eth0, note ifup will regard it a
>>> manual operation for the nic specified in 1st argument if there's
>>> the 2nd argument.
>>>
>>> If same nic is used for netroot the 2nd argument will be ignored,
>>> in this case we will leave netroot bring up it automatically to
>>> avoid side effect. And in this case hooks such as kdump will need to
>>> execute after netroot mounted.
>>>
>>> `ifup eth0 -m` will create /tmp/net.eth0.manualup stamp file,
>>> later dhclient-script can check this and pass $2 to netroot,
>>> then netroot script will bring eth0 up
>>>
>>
>> As we talked on IRC, we still need to discuss if this is really
>> needed, from kdump perspective.
> 
> 
> manually ifup nic also benefit to emergency shell use case. I want to
> use dracut initramfs as a minimal system without real root for kernel
> testing
> 
>> 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.
> 
> If we just bring up all nics, then use the manual ifup is also easy.
> 
> current dracut udev rules is: if there's no nic specified it will ifup
> all possible nics, but all will be put in initqueue which finally be
> brought up by netroot script.


And if without netroot cmdline set netroot script will just fail and
return, so in this case ifup will act as nop

> 
>>
>> Let's see what Harald thinks...
> 
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe initramfs" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> 



-- 
Thanks
Dave

  parent reply	other threads:[~2012-01-11  2:08 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 [this message]
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

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=4F0CEF14.5030206@redhat.com \
    --to=dyoung-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@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