On Fri, Oct 16, 2009 at 04:33:13PM +0100, Ben Hutchings wrote: > On Fri, 2009-10-16 at 09:20 -0600, dann frazier wrote: > > On Fri, Oct 16, 2009 at 07:32:50PM +0530, Narendra_K@xxxxxxxx wrote: > [...] > > > And how would the regular file look like in terms of holding ifindex of > > > the interface, which can be passed to libnetdevname. > > > > I can't think of anything we need to store in the regular file. If we > > have the kernel name for the device, we can look up the ifindex in > > /sys. Correct me if I'm wrong, but storing it ourselves seems > > redundant. > > But the name of a netdev can change whereas its ifindex never does. > Identifying netdevs by name would require additional work to update the > links when a netdev is renamed and would still be prone to race > conditions. This is why Narendra and Matt were proposing to store the > ifindex in the node all along... Matt, Ben and I talked about a few other possibilities on IRC. The one I like the most at the moment is an idea Ben had to creat dummy files named after the ifindex. Then, use symlinks for the kernel name and the various by-$property subdirectories. This means the KOBJ events will need to expose the ifindex. I'm a novice at net programming, but I'm told that ifindex is the information apps ultimately require here. -- dann frazier -- 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
