From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Tue, 14 Aug 2007 07:17:06 +0000 Subject: Re: ANNOUNCE: bios_dev_name 0.2, now with more SMBIOS goodness Message-Id: <20070814071706.GA16416@kroah.com> List-Id: References: <20070728040323.GA25467@auslistsprd01.us.dell.com> In-Reply-To: <20070728040323.GA25467@auslistsprd01.us.dell.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Mon, Aug 13, 2007 at 09:57:53PM -0500, Matt Domsch wrote: > On Mon, Aug 06, 2007 at 09:37:08AM -0500, Matt Domsch wrote: > > On Fri, Jul 27, 2007 at 11:03:23PM -0500, Matt Domsch wrote: > > > You may recall a problem several hardware manufacturers faced, where > > > the BIOS-given name for an ethernet device (e.g. "Gb1") didn't map to > > > the expected and obvious Linux device name (e.g. eth0), but instead > > > mapped to another name (e.g. eth1). This was highly confusing to > > > system admins with such hardware. > > > > [snip] > > > > > so now, option 3: > > > > > > 3) bios_dev_name (http://linux.dell.com/files/bios_dev_name) - > > > intended to be a udev helper. For example, something like: > > > > > > KERNEL="eth*", ACTION="add", PROGRAM="/usr/sbin/bios_dev_name -i %k", NAME="%c" > > > > > > which, given the kernel's name for a device, retreives the > > > BIOS-expected name, and sets it to that. Alternately, it can be > > > integrated into SuSE's rename_netiface script as demonstrated in the > > > patch included in the release. As a udev helper, it doesn't need > > > config files to accomplish its work. > > I'd appreciate any feedback people have on this. I've gotten one > report of it working for someone with both Dell and non-Dell hardware > on Debian. I think it solves a real problem, cleanly. I have no objection to this solution, but I'm a little unclear as to what you want us to do about this? Do you want to add this to the udev tree? If so, send a patch. But you asked that it go into distros, and the developers here, while some do work for distros, the proper way to achieve this is to probably go through the different company "add a feature" request proceedure. thanks, greg k-h ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel