Le 20/08/2017 à 16:27, Adam Borowski a écrit :
> Thus, I think the best long-term solution would be writing a generation,
> using either *udev or ifupdown, that learns new interfaces as they come,
> and names them using a single namespace that's not "eth0"/"wlan0".
> In particular, a machine with only a single interface (ie, 99% of them)
> would predictably have en0 and possibly wl0.
>
> But sticking with just kernel names would still be much better than the
> enp0s3 idea. It'd be _predictable_ in that 99% case; machines with multiple
> interfaces tend to be either routers (which come preconfigured) or servers
> (which have an admin who's supposed to have a clue).
>
There was already a name generation by Udev, based on the MAC
address, but it used the same namespace as the kernel, eg, renaming eth0
to eth1 when the MAC changed. AFAIU, this was and is still considered a
problem.
Didier
::
Re: [DNG] Proposed change in behavi…
