| 1 |
Tom H <tomh0665@×××××.com> writes: |
| 2 |
|
| 3 |
> On Thu, Dec 22, 2016 at 3:56 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 4 |
>> On Thu, 22 Dec 2016 04:15:50 +0100, lee wrote: |
| 5 |
>>> |
| 6 |
>>> The perceived advantage lies in being able to refer to network ports |
| 7 |
>>> in a more reliable way, and I don't see how using unrecognisable |
| 8 |
>>> names instead of recognisable ones would make anything easier. |
| 9 |
>> |
| 10 |
>> See above re automation. It doesn't really matter whether you see the |
| 11 |
>> need or not. If you don't have the need, don't use it, they are an |
| 12 |
>> option for those who do want them. |
| 13 |
> |
| 14 |
> All of this whining about predictable NIC names would be more or less |
| 15 |
> OK if there wasn't an easy way to override them in |
| 16 |
> "/{lib,etc}/systemd/network/" (even on a non-systemd system, see [1]) |
| 17 |
> or in "/etc/udev/rules.d/"! |
| 18 |
> |
| 19 |
> [1] There's no need to learn/use the udev rules syntax. I use the |
| 20 |
> following in "/etc/systemd/network/" on a Debian 8 system with |
| 21 |
> sysvinit-as-pid1: |
| 22 |
> |
| 23 |
> [Match] |
| 24 |
> MACAddress=can't_be_bothered_to_look_it_up |
| 25 |
> [Link] |
| 26 |
> Name=en0 |
| 27 |
|
| 28 |
Thanks! |
| 29 |
|
| 30 |
What happens when you replace the card with another one that has a |
| 31 |
different MAC? Shouldn't an assignment like this rather go by the |
| 32 |
unrecognisable name? I'd find that more consistent. |
Archives