| 1 |
Andrej Rode <mail@××××××××.de> writes: |
| 2 |
|
| 3 |
>>> It is even more frustrating that these so-called predictable network |
| 4 |
>>> names actually can change on a reboot, it's happened to me more than |
| 5 |
>>> once when multiple network cards are detected in a different order. |
| 6 |
> |
| 7 |
> Then you might found a bug? With predictable network names the name of |
| 8 |
> your device depends on the PCIe slot/address it is in. If you change |
| 9 |
> positions in the board your names should change, not on reboot. |
| 10 |
|
| 11 |
It wasn't me who said that. |
| 12 |
|
| 13 |
> And you might believe it or not, running Linux on servers is much more |
| 14 |
> popular than running Linux on your home desktop. Thus I'd guess things |
| 15 |
> tend to be made easier for people with more than one network card. |
| 16 |
> Certainly you don't want rely on random device enumeration order on |
| 17 |
> reboot if you run a webserver with multiple network devices. |
| 18 |
|
| 19 |
The point is that replacing recognisable names with unrecognisable ones |
| 20 |
doesn't make things easier, regardless of how many network ports you |
| 21 |
have. |
| 22 |
|
| 23 |
Or can you explain how unrecognisable names make things easier? |
| 24 |
|
| 25 |
> If you want to disable this on hosts running systemd read [0]. |
| 26 |
|
| 27 |
I'm not using systemd. |
| 28 |
|
| 29 |
> Cheers, |
| 30 |
> Andrej |
| 31 |
> |
| 32 |
> [0] |
| 33 |
> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ |
Archives