>Sure, it's never guaranteed by the kernel that this will >happen, especially as we speed up the boot process by doing >things async. >So again, just fix your installer, or write a new udev rule >for your hardware platforms, or both. But I still fail to see >why multiple names for network devices _in the kernel_ is a >solution for your issue. > The char device nodes solution does not propose having multiple names for the network interfaces _in the kernel_. It is suggesting that we have alternate names for kernel assigned names in user space and user space utilities refer to the interface by these alternate names. The userspace utilities would have to map the pathnames to kernel names before issuing the ioctls. That way there is determinism without embedding MAC or any other attribute. An Embedded_NIC_1 interface would always refer to the Gb1 without having to depend on any attribute. With regards, Narendra K -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
