On Tue, Jun 25, 2019 at 11:09:12AM +0200, Hans wrote:
Might be, but this does not explain, why there are still scripts and configurations, which are still using the old names. And THAT is the problem.
It isn't because:1) the new names are predictable but not constant, so you can't configure a single default across all systems 2) most software doesn't care about interfaces, so doesn't need to have an interface configured 3) software that does care about interfaces generally needs some additional configuration, so the defaults aren't relevant 4) if there are isolated exceptions, they can be dealt with as they are noticed. if software is used so little that nobody has noticed that it's not working, there are probably bigger issues with the package.
The default (Debian /has/ to settle for one default, since many people installing Debian don't know or care what an interface name is, let alone what the heck a /predictable interface name/ is), is "predictable interface names".Yes, I wrote about it. And I also told my opinion about it: If people shall use it, why change to predictable names? That makes no sense.
They are tremendously helpful if you build servers with multiple interfaces, or you ever have to swap out a broken nic. If you have a simple system it gets set once at install time, so who cares?