| 1 |
On 29/03/13 12:46, Diego Elio Pettenò wrote: |
| 2 |
> On 29/03/2013 11:26, Samuli Suominen wrote: |
| 3 |
>> With the new predictable network interface naming scheme which upstream enabled |
| 4 |
>> by default you don't have to rename anymore because the names will be static |
| 5 |
>> and not randomly rename when you, for example, upgrade the kernel. This can be |
| 6 |
>> very important aspect, for example, security in mind. |
| 7 |
> |
| 8 |
> You do know this is false, right? The names are supposed to be |
| 9 |
> predictable, not persistent. If you do happen to MOVE your network card |
| 10 |
> because the new videocard you add to your system does not fit otherwise, |
| 11 |
> the name _will_ change. |
| 12 |
|
| 13 |
Not false, but configurable, and linked from the news item -- nobody |
| 14 |
stopping you from eg. using MAC addresses instead of PCI slots for |
| 15 |
defining the names, just like one would have renamed them using MAC with |
| 16 |
70-persistent-net.rules |
| 17 |
|
| 18 |
>> If /etc/udev/rules.d/80-net-name-slot.rules is a empty file, or if it's a |
| 19 |
>> symlink to /dev/null, the new names will be disabled and kernel will do |
| 20 |
>> all the interface naming, which will be random. |
| 21 |
> |
| 22 |
> Avoid spreading FUD about naming being random. Thanks. |
| 23 |
|
| 24 |
Not FUD, but a fact, depends on the driver code (in kernel) if it'll |
| 25 |
change or not |
| 26 |
That's random enough as we can't force people to track kernel source |
| 27 |
tree and drivers code |
Archives