| 1 |
On Tue, Dec 27, 2016 at 1:53 PM, lee <lee@××××××××.de> wrote: |
| 2 |
> Neil Bothwick <neil@××××××××××.uk> writes: |
| 3 |
>> |
| 4 |
>> There is nothing wrong with wanting things to work as you do, but it |
| 5 |
>> requires input to do so. It you have to start editing files to make |
| 6 |
>> it work properly, there is little point in making it the default. |
| 7 |
> |
| 8 |
> Right, and it could work without editing files manually. A |
| 9 |
> configuration file assigning editable names to the annoying names |
| 10 |
> could be created automatically and filled by assigning the name an |
| 11 |
> interface already has to it (because when it has a name, the name is |
| 12 |
> known, which is easier than trying to make up all possible names in |
| 13 |
> advance). Then only if you wanted you would edit the configuration |
| 14 |
> file to assign the name(s) of your choosing, and if you don't want to |
| 15 |
> do that, you simply get the names you get now. There would be no |
| 16 |
> change to how the names are now, only an additional option. |
| 17 |
> |
| 18 |
> That would also have the advantage that when the annoying name of an |
| 19 |
> interface changes, you can choose to either adjust all configuration |
| 20 |
> files in which you have specified a particular interface or simply |
| 21 |
> adjust the one configuration file that assigns the names. |
| 22 |
|
| 23 |
There are two ways to ensure that you always have the kernel's names: |
| 24 |
|
| 25 |
1) Add "net.ifnames=0" to the kernel cmdline |
| 26 |
|
| 27 |
2) Override "NamePolicy=..." in "/lib/systemd/network/99-default.link" |
| 28 |
with "NamePolicy=kernel" in "/etc/systemd/network/99-default.link". |
Archives