Hi,

As I am reading this discussion a temptative thought is coming to my
mind which is: what can Devuan do to avoid this new device naming
scheme breaking breaking software that rely on the old naming
convention?

As I wrote in my earlier reply, I am ready to offer my help in this,
provided the coding task is within my reach.

Edward

On 10/01/2016, Rainer Weikusat <rainerweikusat@???> wrote:
> Rainer Weikusat <rainerweikusat@???> writes:
>
> [ethX reordering]
>
>> in the relative rare case that more than one network driver actually
>> has to be loaded, if the order in which the drivers call their init
>> routines changes. There's nothing which would stop "driver loading
>> support software" from ensuring that this won't happen gratuitiously.
>
> Afterthought: Considering that the kernel has to serialize these init
> calls, anyway, so that it can assign unique numbers, this great
> "performance optimization" actually just ends up with creating avoidable
> lock contention.
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>