On Mon, 26 Dec 2016 21:01:22 +0100, lee wrote: > > AFAIK, you have three possibilities. > > > > 1) If you're renaming a NIC via its MAC address, you have to edit the > > config file thatlinks the NIC's names and its MAC address. > > > > 2) If you're using udev's predictable names, the NIC'll have the same > > (more or less complex) name if you use the same slot. > > > > 3) If you're using the kernel names, you have no guarantee that ethX > > will be assigned to the same NIC at every bot. > > So there's no good option because names may change unless you make and > maintain an assignment. I wonder why that isn't the default ...
I would imagine because it cannot be used without some initial configuration. The default provides the greatest reliability out of the box, at the expense of less readable (which is not the same as unrecognisable, a value judgement you are imposing on the names) names. There is nothing wrong with wanting things to work as you do, but it requires input to do so. It you have to start editing files to make it work properly, there is little point in making it the default. -- Neil Bothwick GOTO: (n.) an efficient and general way of controlling a program, much despised by academics and others whose brains have been ruined by overexposure to Pascal.
pgp5fSFWYrnWV.pgp
Description: OpenPGP digital signature
