Does this mean now Ethernet devices will have three possible interface names?
Why can't they write a udev rule to do naming based on bus location to the proper eth?
Also, I like how udev does /dev/disk and gives each device 4 names by-id, by-label, by-path, and by-uuid. These are all sym links to the Actual device like sda1. Yet, I am unaware of a way to give a Network device a second name similar to doing a sum link to a char or block device.
And no our scripts were not broken and even if we used variables for interface names this is still annoying.