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.
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
