Per Jessen wrote:
Linda Walsh wrote:
Roger Oberholtzer wrote:
I think it is the order the BIOS discovers/lists the cards. We have some SuperMicro MBs where each boot the drivers may be loaded in a different order. Then ethX moves around and we are not happy campers. The new naming has been a very good thing for us as our systems reboot at least once a day. The kernel naming is not usable as it is not consistent across boots.
I have a bash script I run as part of my boot procedure that checks the hardware-ethernet addrs and renames them.
Do you have a reason for not just using the udev renaming?
Because every once in a while, some piece of the udev software got updated and remangled the names. It wasn't _that_ often, but the more often I updated the more likely some upgrade would cause it to change things. News about what's going to happen to network naming has gone back and forth as well, intermixed with new upstream SW that hasn't always been reliably tested and certainly hasn't been vetted for compatibility (fairly obvious that is not high on the priority list). With the udev being integrated into systemd, it's future stability doesn't seem likely to improve... So... the script simply says to heck with the chaos and tries to go with something *nix is good at -- using scripting to fix and manage things. Having it in script also makes it easier to debug if something goes wrong or changes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org