biosdevname hitting rawhide
Matt_Domsch at dell.com
Tue Nov 30 21:20:12 UTC 2010
On Tue, Nov 30, 2010 at 10:13:30PM +0100, Fabian Deutsch wrote:
> Good day,
> Am Dienstag, den 30.11.2010, 13:04 -0600 schrieb Matt Domsch:
> > On Mon, Nov 29, 2010 at 08:48:05PM +0530, Rahul Sundaram wrote:
> > > On 11/29/2010 08:27 PM, Matt Domsch wrote:
> > > > On Mon, Nov 29, 2010 at 12:17:22AM -0600, Matt Domsch wrote:
> > > >> I've just pushed biosdevname-0.3.1 into rawhide. This is not yet
> > > >> installed by default as part of @base, nor is it used by anaconda, but
> > > >> those changes will come over the next few days.
> > > > I've pushed the comps change to pull biosdevname into @base by
> > > > default. And I've posted a patch to anaconda-devel-list to pull
> > > > biosdevname into the installtime environment. Cross your fingers,
> > > > this is gonna be great!
> > >
> > > Can you expand the release notes section of
> > >
> > > http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming
> > >
> > > Please include the benefits in that.
> > Done.
> I was curious and ran
> $ sudo biosdevname -i wlan0
> Does that mean that my wlan0 device would be named em1 when installing -
> lets say - F15?
> If so, this change would affect many users I suppose.
> Could you clarify what hardware is affected and what devices will get
> different names?
Can I get a dmidecode dump? Curious... That could be hitting a legacy
codepath that I need to delete (looking up the value in the PCI IRQ
Routing Table). My intention is to only report for devices that the
BIOS explicitly exposes via SMBIOS, or in future, ACPI.
Dell | Office of the CTO
More information about the devel