diff options
| author | LennartPoettering <LennartPoettering@web> | 2013-09-10 03:52:06 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2018-12-11 10:58:40 +0100 |
| commit | 8745120c9901be20f742dd78d5578d5f3d768df5 (patch) | |
| tree | d9e791bef77500e3b180f0842d1144aa0a8f7138 | |
| parent | (no commit message) (diff) | |
| download | systemd-8745120c9901be20f742dd78d5578d5f3d768df5.tar.xz systemd-8745120c9901be20f742dd78d5578d5f3d768df5.zip | |
Diffstat (limited to '')
| -rw-r--r-- | docs/PredictableNetworkInterfaceNames.mdwn | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/PredictableNetworkInterfaceNames.mdwn b/docs/PredictableNetworkInterfaceNames.mdwn index 5f8a4f95e4..8db4e1d8ad 100644 --- a/docs/PredictableNetworkInterfaceNames.mdwn +++ b/docs/PredictableNetworkInterfaceNames.mdwn @@ -49,7 +49,8 @@ With this new scheme you now get: * The network interface naming now follows more closely the scheme used for aliasing block device nodes and other device nodes in /dev via symlinks * Applicability to both x86 and non-x86 machines * The same on all distributions that adopted systemd/udev -* It's easy to opt out of the scheme (see below) +* It's easy to opt out of the scheme (see below) + Does this have any drawbacks? Yes, it does. Previously it was practically guaranteed that hosts equipped with a single ethernet card only had a single "eth0" interface. With this new scheme in place, an administrator now has to check first what the local interface name is before he can invoke commands on it where previously he had a good chance that "eth0" was the right name. |