| 1 |
On Wed, 21 Dec 2016 22:48:29 +0100, lee wrote: |
| 2 |
|
| 3 |
> > You can't switch any two names because the udev rules are run singly, |
| 4 |
> > so at one point you will be trying to rename an interface with a name |
| 5 |
> > that is already in use. |
| 6 |
> |
| 7 |
> I mean more like renaming them on the fly --- or by having a |
| 8 |
> configuration file with key:value pairs like 'enp69s0f1:eth3' --- or |
| 9 |
> perhaps triples like 'enp69s0f1:eth3:"DMZ Interface"'. |
| 10 |
|
| 11 |
In that case you may as well leave the unique names in place and set up |
| 12 |
recognisable aliases. |
| 13 |
|
| 14 |
> That way, you could have a recognisable name (or several names) for |
| 15 |
> every unrecognisable one and assume that "eth3" or "foo" or however you |
| 16 |
> want to call it is the same interface just as much as you would with |
| 17 |
> unrecognisable names --- plus the advantage that when you ever need to |
| 18 |
> change an interface, you only need to edit one small file rather than |
| 19 |
> various configurations files having the unrecognisable name(s) in them. |
| 20 |
|
| 21 |
There are no config files to edit with the predictable names, the names |
| 22 |
are created from the physical location of the port. That's why they are |
| 23 |
called predictable, unless you move the NIC to a different PCI slot, it |
| 24 |
will always have the same name, no matter what other hardware you add or |
| 25 |
remove. Yes, the names are cumbersome, but they have to be like that to |
| 26 |
guarantee their uniqueness. How often you you have to type interface |
| 27 |
names anyway, and how many of those are in a shell with tab completion |
| 28 |
that takes care of it for you? |
| 29 |
|
| 30 |
The names are ugly, but that's about their only sin. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Neil Bothwick |
| 35 |
|
| 36 |
Head: (n.) the part of a disk drive which detects sectors and decides |
| 37 |
which of the two possible values to return: 'lose a turn' or 'bankrupt.' |
Archives