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