picnoir/Systemd
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Browse source
This commit is contained in:
LennartPoettering 2013-01-07 21:36:45 +00:00 committed by Zbigniew Jędrzejewski-Szmek
parent 2d2111748f
commit 648f251ff9
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/PredictableNetworkInterfaceNames.moin
View file

@ -18,11 +18,11 @@ We believe it is a good default choice to generalize the scheme pioneered by "bi
With systemd 197 we have moved a scheme similar to biosdevname (put generally more powerful) into systemd/udev proper. A number of different naming schemes for network interfaces are now supported by udev natively:
1. Names incorporating Firmware/BIOS provided index numbers for on-board devices
2. Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers
3. Names incorporating physical/geographical location of the connector of the hardware
4. Names incorporating the interfaces's MAC address
5. Classic, unpredictable kernel-native ethX naming
1. Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: {{{eno1}}})
2. Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: {{{ens1}}})
3. Names incorporating physical/geographical location of the connector of the hardware (example: {{{enp2s0}}})
4. Names incorporating the interfaces's MAC address (example: {{{enx78e7d1ea46da}}})
5. Classic, unpredictable kernel-native ethX naming (example: {{{eth0}}})
By default, systemd v197 will now name interfaces following policy 1) if that information from the firmware is applicable and available, falling back to 2) if that information from the firmware is applicable and available, falling back to 3) if applicable, falling back to 5) in all other cases. Policy 4) is not used by default, but is available if the user chooses so.