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