| 1 |
On Fri, Dec 23, 2016 at 9:07 PM, lee <lee@××××××××.de> wrote: |
| 2 |
> Tom H <tomh0665@×××××.com> writes: |
| 3 |
>> On Mon, Dec 19, 2016 at 3:07 PM, Daniel Frey <djqfrey@×××××.com> wrote: |
| 4 |
>>> |
| 5 |
>>> It is even more frustrating that these so-called predictable network |
| 6 |
>>> names actually can change on a reboot, it's happened to me more than |
| 7 |
>>> once when multiple network cards are detected in a different order. |
| 8 |
>> |
| 9 |
>>>From Kay Sievers in [1]: |
| 10 |
>> |
| 11 |
>> <BEGIN> |
| 12 |
>> Btw, predictable means it will not change between reboots, that names |
| 13 |
>> will not depend on enumeration order within the same setup. It does |
| 14 |
>> not mean or promise, that added kernel/driver/firmware features will |
| 15 |
>> not result in different names. That is expected behavior. |
| 16 |
>> </END> |
| 17 |
>> |
| 18 |
>> [1] https://lists.freedesktop.org/archives/systemd-devel/2015-October/034614.html |
| 19 |
> |
| 20 |
> So the names will not change when rebooting and are to be expected to |
| 21 |
> possibly change at any time. |
| 22 |
> |
| 23 |
> How is that more reliable? |
| 24 |
|
| 25 |
It's more reliable than using the kernel's names because the names |
| 26 |
won't change UNLESS there's kernel/driver/firmware change for that |
| 27 |
NIC. I doubt that these changes occur that often. Perhaps someone else |
| 28 |
knows. |
Archives