On Mon, 2012-02-06 at 16:43 +0800, Dave Young wrote: > On 02/06/2012 03:53 PM, Cong Wang wrote: > > > On 02/06/2012 03:51 PM, Dave Young wrote: > >> I think the key problem is the network setup code split. I would not > >> insist on this although I don't like that we must add ip= to have > >> network setup > > > > With your patches, we must have rd.neednet=1. :) So, it is unfair to > > only blame ip= approach. > > > I mean for netroot we also must have ip= set because ip= will deal with > the network setup. Originally we might have no ip= but with proper > netroot param like root=nfs... In that case, we do DHCP and it works. Having ip=BLAH on the command line is not a requirement. As for rdbreak=cmdline, I expect that to be used by experts debugging dracut issues, and they should be knowledgeable enough to manually configure the network if they need it. I don't believe an automated solution is required there. That's not to say a script to do the right thing wouldn't be useful, just not high on the list of things to do. I could easily envision a "helper script" that runs through the command line arguments (perhaps using the existing hooks) and brings up the network. But I see it as more of a user-run command than an automated step. -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
