Marco Rebhan wrote: > On Wednesday, 1 December 2021 20:44:48 CET Arve Barsnes wrote: >> I have been running eudev for as long as it has existed, and have also >> been using the predictable interface names more or less since they >> were introduced. The eudev ebuild also shows a message about this >> every single time you emerge it (with ewarn messages in pkg_pretend). >> This was apparently available in eudev within a month of the change >> in systemd. No one should be surprised by this. > Yeah, I was wondering why people were hitting this problem, the > predictable interface names have been in eudev as well for a > considerable while. I had them disabled with the same net.ifnames=0 that > others are mentioning now to get the old names (mainly since they're > just easier to remember). I was maybe thinking that there could be a > configuration option for it that didn't get changed on existing installs > when this was initially introduced in eudev, which would have explained > it since my installs aren't that old. But if it automatically used the > new names for you then I have no idea either. Nothing should have > changed in this regard with this update as far as I can tell... > > -Marco
What made this affect me, I think the method is different to disable it in udev than it is in eudev. I had something set, not on the kernel line tho, to disable it on mine when using eudev. I think it is a udev rules file. Thing is, when I rebooted with udev installed, it ignored the method eudev uses and used the newer naming method. If the same option worked for both, then I would likely have seen no difference at all. I might add, that is what I was expecting and was surprised to find it not to be the case. When I switched from udev to eudev ages ago, I did nothing but remove udev and install eudev. That's it. I don't recall changing anything else but that was ages ago. I'm hoping others doing this switch will notice my thread and this thread to prevent them from switching and not realizing it can break things until it is configured correctly. Bad thing is, it breaks one thing that is needed to get help, the connection to the internet. If it is a remote machine, that is really bad. Let's hope this alerts others to double and maybe even triple check things before rebooting. Dale :-) :-)
