* Re: [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt
@ 2013-03-29 10:50 99% ` Samuli Suominen
0 siblings, 0 replies; 1+ results
From: Samuli Suominen @ 2013-03-29 10:50 UTC (permalink / raw
To: gentoo-dev
On 29/03/13 12:46, Diego Elio Pettenò wrote:
> On 29/03/2013 11:26, Samuli Suominen wrote:
>> With the new predictable network interface naming scheme which upstream enabled
>> by default you don't have to rename anymore because the names will be static
>> and not randomly rename when you, for example, upgrade the kernel. This can be
>> very important aspect, for example, security in mind.
>
> You do know this is false, right? The names are supposed to be
> predictable, not persistent. If you do happen to MOVE your network card
> because the new videocard you add to your system does not fit otherwise,
> the name _will_ change.
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
>> If /etc/udev/rules.d/80-net-name-slot.rules is a empty file, or if it's a
>> symlink to /dev/null, the new names will be disabled and kernel will do
>> all the interface naming, which will be random.
>
> Avoid spreading FUD about naming being random. Thanks.
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
^ 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 99% ` Samuli Suominen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox