* Re: [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt
@ 2013-03-29 11:01 99% ` Diego Elio Pettenò
0 siblings, 0 replies; 1+ results
From: Diego Elio Pettenò @ 2013-03-29 11:01 UTC (permalink / raw
To: gentoo-dev
On 29/03/2013 11:50, Samuli Suominen wrote:
> Not false, but configurable, and linked from the news item -- nobody
> stopping you from eg. using MAC addresses instead of PCI slots for
> defining the names, just like one would have renamed them using MAC with
> 70-persistent-net.rules
Which I usually do. But
"With the new predictable ... scheme ... the names will be static and
not randomly rename ..."
is false.
The name will be predictable before rebooting (maybe?) but it could very
easily change randomly on udev update.
> Not FUD, but a fact, depends on the driver code (in kernel) if it'll
> change or not
> That's random enough as we can't force people to track kernel source
> tree and drivers code
Hm hm. It's still FUD.
If my desktop only has one Ethernet interface, no matter how many kernel
changes happen, it'll always be eth0.
Whereas, with the new predictable scheme, if I move that card around, it
will change name.
Tell me which one is random, again?
---
I'm not saying you shouldn't enable it (feel free to screw up user as
much as you want, just don't complain if they don't like you), but since
both kernel naming and predictable naming have their chance to change,
don't spread FUD.
--
Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2013-03-29 8:09 [gentoo-dev] Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt Samuli Suominen
2013-03-29 10:24 ` [gentoo-dev] " Duncan
2013-03-29 10:26 ` Samuli Suominen
2013-03-29 10:46 ` Diego Elio Pettenò
2013-03-29 10:50 ` Samuli Suominen
2013-03-29 11:01 99% ` Diego Elio Pettenò
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox