On Thu, Aug 26, 2010 at 17:38, Loke, Chetan <Chetan.Loke@xxxxxxxxxxxx> wrote: > Sorry, my bad. > I agree w/ your recommendation then - > 1) stuff it in ifalias(or create a new alias if net_device::ifalias is > used for snmp etc). > > But how do we consume it? > 1.1) spit it out via sysfs? But Doc/sysfsrules.txt says "Accessing > /sys/class/net/eth0/device is a bug in the application" You walk up the parent devices of the netdev until you find the one you are looking for. The "device" link is broken by design and might just point to the first parent device. The kernel is free to insert devices into the device tree if needed, and then the device link target may change. /sys/class/net/eth0 is a symlink pointing to a location the /sys/devices tree, like: ../../devices/pci0000:00/0000:00:19.0/net/eth0 One of the parent devices of the eth0 device has this attribute., but you can never be sure that it's just the next parent (broken concept of the device link), you have to walk up the chain of parents. You can just use udev to that automatically and extract the value, and pass it with the event for the eth0 device. Kay -- 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
