1 |
Neil Bothwick <neil@××××××××××.uk> writes: |
2 |
|
3 |
> On Mon, 26 Dec 2016 21:01:22 +0100, lee wrote: |
4 |
> |
5 |
>> > AFAIK, you have three possibilities. |
6 |
>> > |
7 |
>> > 1) If you're renaming a NIC via its MAC address, you have to edit the |
8 |
>> > config file thatlinks the NIC's names and its MAC address. |
9 |
>> > |
10 |
>> > 2) If you're using udev's predictable names, the NIC'll have the same |
11 |
>> > (more or less complex) name if you use the same slot. |
12 |
>> > |
13 |
>> > 3) If you're using the kernel names, you have no guarantee that ethX |
14 |
>> > will be assigned to the same NIC at every bot. |
15 |
>> |
16 |
>> So there's no good option because names may change unless you make and |
17 |
>> maintain an assignment. I wonder why that isn't the default ... |
18 |
> |
19 |
> I would imagine because it cannot be used without some initial |
20 |
> configuration. The default provides the greatest reliability out of the |
21 |
> box, at the expense of less readable (which is not the same as |
22 |
> unrecognisable, a value judgement you are imposing on the names) names. |
23 |
|
24 |
I call them unrecognisable because they are hard to recognise, as in |
25 |
hard to read and impossible to remember. I find that annoying. I can |
26 |
call them "annoying names" if you prefer that :) |
27 |
|
28 |
> There is nothing wrong with wanting things to work as you do, but it |
29 |
> requires input to do so. It you have to start editing files to make it |
30 |
> work properly, there is little point in making it the default. |
31 |
|
32 |
Right, and it could work without editing files manually. A |
33 |
configuration file assigning editable names to the annoying names could |
34 |
be created automatically and filled by assigning the name an interface |
35 |
already has to it (because when it has a name, the name is known, which |
36 |
is easier than trying to make up all possible names in advance). Then |
37 |
only if you wanted you would edit the configuration file to assign the |
38 |
name(s) of your choosing, and if you don't want to do that, you simply |
39 |
get the names you get now. There would be no change to how the names |
40 |
are now, only an additional option. |
41 |
|
42 |
That would also have the advantage that when the annoying name of an |
43 |
interface changes, you can choose to either adjust all configuration |
44 |
files in which you have specified a particular interface or simply |
45 |
adjust the one configuration file that assigns the names. |
46 |
|
47 |
I actually wonder why they didn't virtualise the names. It makes too |
48 |
much sense for not to do it, and you could do likewise with other |
49 |
devices (especially disks). |