diff options
author | LennartPoettering <mzninuv@0pointer.de> | 2013-01-22 21:22:48 +0100 |
---|---|---|
committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2018-12-11 10:58:40 +0100 |
commit | 54313217c1f499550c20c38b19a18c5058f9e9ca (patch) | |
tree | 729509a11e29a3d6c25c7f22d6b3d35408ee3a37 | |
parent | (no commit message) (diff) | |
download | systemd-54313217c1f499550c20c38b19a18c5058f9e9ca.tar.xz systemd-54313217c1f499550c20c38b19a18c5058f9e9ca.zip |
-rw-r--r-- | docs/PredictableNetworkInterfaceNames.moin | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/PredictableNetworkInterfaceNames.moin b/docs/PredictableNetworkInterfaceNames.moin index cefd166cec..08b6707cb7 100644 --- a/docs/PredictableNetworkInterfaceNames.moin +++ b/docs/PredictableNetworkInterfaceNames.moin @@ -47,7 +47,7 @@ With this new scheme you now get: * The same on all distributions that adopted systemd/udev * 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. 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. +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. == I don't like this, how do I disable this? == |