linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: ANNOUNCE: bios_dev_name 0.2, now with more SMBIOS goodness
Date: Tue, 14 Aug 2007 07:17:06 +0000	[thread overview]
Message-ID: <20070814071706.GA16416@kroah.com> (raw)
In-Reply-To: <20070728040323.GA25467@auslistsprd01.us.dell.com>

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

  parent reply	other threads:[~2007-08-14  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-28  4:03 ANNOUNCE: bios_dev_name 0.2, now with more SMBIOS goodness Matt Domsch
2007-08-06 14:37 ` Matt Domsch
2007-08-14  2:57 ` Matt Domsch
2007-08-14  7:17 ` Greg KH [this message]
2007-08-14  8:53 ` Kay Sievers

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=20070814071706.GA16416@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).