On 12/19/2016 01:09 PM, Andrej Rode wrote: > >>> It is even more frustrating that these so-called predictable network >>> names actually can change on a reboot, it's happened to me more than >>> once when multiple network cards are detected in a different order. > > Then you might found a bug? With predictable network names the name of > your device depends on the PCIe slot/address it is in. If you change > positions in the board your names should change, not on reboot. > > And you might believe it or not, running Linux on servers is much more > popular than running Linux on your home desktop. Thus I'd guess things > tend to be made easier for people with more than one network card. > Certainly you don't want rely on random device enumeration order on > reboot if you run a webserver with multiple network devices. > > If you want to disable this on hosts running systemd read [0]. > > Cheers, > Andrej > > [0] > https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ >
It could be I found a bug. After a reboot it went from the normal enp0s1 (or whatever) to eno1677789 or something ridiculous. I had this happen on two different machines. I tried systemd on a couple machines to see what the hubbub was about, and on one machine it crashed on reboot. I probably forgot something, but alas, I'd already removed openrc and found out about the binary logs. I had no way to download something that supported systemd at the time so I could view the log. Went back to openrc on that machine and disabled that stupid predictable name junk. When you only have one network interface, it's rather silly. That should have been by default off, server administrators could turn it back on. For what it's worth, systemd works fine on my 11-year-old laptop. It had issues with my desktop (which is almost 9 years old now) but I really don't know if it was related to mdadm, or ??? I thought I had it figured out on my desktop but on reboot systemd wouldn't mark my IMSM mdadm array as clean leading to a disk thrashing every time I rebooted, making my computer almost unusable. Dan
