В Mon, 02 Mar 2015 19:46:51 +0100 Per Jessen firstname.lastname@example.org пишет:
John Andersen wrote:
On 03/02/2015 12:52 AM, Felix Miata wrote:
You don't need to use bizarro NIC names like enp5s0 if you don't want.
Personally, I like the bizarro rules. (There's always SOMEBODY ;-)
Gotten use to them with openbsd, and they aren't as bizarro as they first seem. You can just look at the nic to know which name its using and know which cable goes there.
Even if I look directly at the port and it is numbered, I am unable to work out which bizarro name it is likely to have.
If your system supports returning slot names, you should get sX for them. As long as you trust vendor to implement it correctly :)
Except for desktops
and laptops (which both typically have only one interface), I always rename to ethX.
One reason for inventing new names was avoiding name clash with automatic kernel assignment. This still applies. If you do not like "predictable" names (I do not) use something like netXX. But do not use ethXX, as it puts you back on square one. The only case when it is sure to work is when your names are the same as autossigned by kernels, in which case you can simply leave it to kernel in the first place.