One proposal we are looking at is a kernel change to add an extra attribute to the /sys/devices/pciXXX directories. SMBIOS Type 9 and 41 contain mapping between slot number/device name and PCI BDF. Creating an extra attribute called 'slotname' or 'smbiosname' would allow accessing the desired name by /sys/class/net/ethX/device/smbiosname --jordan Hargrave Dell Enterprise Linux Engineering -----Original Message----- From: Jan Engelhardt [mailto:jengelh@xxxxxxxxxx] Sent: Friday, December 18, 2009 8:15 AM To: Domsch, Matt Cc: K, Narendra; be-mail2009@xxxxxxxxxxxx; net-tools@xxxxxxxxxxxx; shemminger@xxxxxxxx; netfilter-devel@xxxxxxxxxxxxxxx; jgarzik@xxxxxxxxxxxxxxxxxxxxx; Rose, Charles; Hargrave, Jordan; Shandilya, Sandeep K Subject: Re: [PROPOSAL]: Alias names for network interfaces On Friday 2009-12-18 15:08, Domsch, Matt wrote: >On Fri, Dec 18, 2009 at 07:42:22AM -0600, Jan Engelhardt wrote: >> >I suppose the ifrename would rename network interfaces from ethN to ethN >> >and that would cause issues. >> >> What issues? > >historically, udev would wind up with NICs named: > >eth0 >eth0_rename >eth2 >eth2_rename > >instead of eth[0-4]. The renames running in parallel would conflict. >I'm told that DavidZ fixed this a recent udev, but I haven't >confirmed this is the case. > >Regardless, this begs the question of how to name newly added NICs. >Today's method involves a human fixing up 70-persistent-net.rules to >match what they want it to be. I hate that, when the platform itself >can provide a perfectly good answer. Of course. If the user chose to want SMBIOS names by default, why not. Except when the BIOS manufacturer left the SMBIOS info blank again. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
