I usually see such things with kernel version changes. In past lives, I've used something like ifrename to handle that situation. I think the modern method is to make (e)udev do it.
On Mon, Aug 21, 2017 at 9:41 AM, Steve Litt <sl...@troubleshooters.com> wrote: > Hi all, > > On another list we're discussing how likely it is to get two identical > NICs reshuffled on boot when using the old style naming (eth0, not > eno1p2s). By reshuffling I mean that last boot's eth0 is now eth1 and > last boot's eth1 is now eth0. One guy with 4.2 billion years of sysvinit > experience said that although it's possible in theory, he's never seen > it happen except when hardware was replaced. > > My question is this: When using inits like runit, s6, s6-rc, > sysvinit+daemontools and the like, is the likelihood of NICs getting > reshuffled on reboot any greater than it would be with sysvinit? > > Thanks, > > SteveT > -- Kevin Berry