------- Comment From prad...@us.ibm.com 2016-04-08 14:24 EDT------- (In reply to comment #23) > > the ideal solution due to the consistency of behavior with the older > > releases > > Just a note: it will behave completely differently to any other network > interface, though, so it's still not consistent at all.
Can you expand on what you mean by it will not be consistent at all? Yes, it will not have names like enP1p160s0f, since it is not a PCI device, but can't it have a name like ethX? This would be in line with expectations from earlier releases. The problem is not really that we are assigning these devices new names, but the device names change with hot plug or DLPAR operations. >ibmveth is a bit of a special child here as it neither has useful hardware >information nor has pre-defined names like "normal" linux veths. Indeed ibmveth device is a special child. Can we use the "DRIVER" match key in a udev rule to name these ibmveth devices as ethX. This will not interfere with the PCI device naming scheme, it will consistently be called ethX and meet prior expectations. Hot plug or DLPAR operations will not impact these with a device name change, and is probably only applicable to the POWER platform. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561096 Title: STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under Ubuntu 16.04 with added adapters (ibmveth) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1561096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
