From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Nottingham Subject: Re: PATCH: Network Device Naming mechanism and policy Date: Mon, 12 Oct 2009 14:07:42 -0400 Message-ID: <20091012180740.GE22736@nostromo.devel.redhat.com> References: <20091009140000.GA18765@mock.linuxdev.us.dell.com> <20091009210909.GA9836@auslistsprd01.us.dell.com> <20091009194401.036da080@nehalam> <20091010044056.GA5350@mock.linuxdev.us.dell.com> <20091010052308.GA12458@kroah.com> <20091012174528.GB22736@nostromo.devel.redhat.com> <20091012175508.GA10946@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Matt Domsch , Stephen Hemminger , netdev@vger.kernel.org, linux-hotplug@vger.kernel.org, Narendra_K@dell.com, jordan_hargrave@dell.com To: Greg KH Return-path: Content-Disposition: inline In-Reply-To: <20091012175508.GA10946@kroah.com> Sender: linux-hotplug-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Greg KH (greg@kroah.com) said: > > No, it's not solved. Even if you have persistent names once you install, > > if you ever re-image, you're likely to get *different* persistent names; > > the first load will always be non-detmerministic. > > > > The only way around this would be to have some sort of screen like: > > > > Would you like your network devices to be enumerated by > > > > [ ] MAC address > > [ ] PCI device order > > [ ] Driver name > > [ ] Other > > [ ] PCI slot name > > That's one that modern systems are now reporting, and should solve > Matt's problem as well, right? ... maybe. On my laptop, the first 'slot' enumerated appears to be the cardbus bridge, before the on-board ethernet. And on the desktop next to me, the slot driver shows nothing. > And I don't see how Matt's proposed patch helps resolve this type of > issue any better than what we currently have today, do you? It allows multiple addressing schemes to be active at once, which can allow the admin to choose post-install without making an active choice at installation. This is an improvement, even if it doesn't solve the world. Bill