[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091012180740.GE22736@nostromo.devel.redhat.com>
Date: Mon, 12 Oct 2009 14:07:42 -0400
From: Bill Nottingham <notting@...hat.com>
To: Greg KH <greg@...ah.com>
Cc: Matt Domsch <Matt_Domsch@...l.com>,
Stephen Hemminger <shemminger@...tta.com>,
netdev@...r.kernel.org, linux-hotplug@...r.kernel.org,
Narendra_K@...l.com, jordan_hargrave@...l.com
Subject: Re: PATCH: Network Device Naming mechanism and policy
Greg KH (greg@...ah.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists