Cathy, In the "kstats after vanity naming" thread from November last year, there was some discussion about how vanity naming would impact kstats... I have a concern or two... Today, if I'm using kstat(3kstat), i can derive the instance number and the name from the interface name. So if someone passes "bge2" into my program, I know that I need to call kstat_lookup like this: kstat_lookup(kc, "bge", 2, "bge2") In the new world of vanity naming, how does one call kstat_lookup()? Specifically, how do i know if I should be calling it like this: kstat_lookup(kc, "link", 0, "net0") Is the way forward to always do the kstat_lookup() call for the 'link' first and follow that up with the old style if that fails?
Or will kstat_lookup() be changing internally so that code that expects interface names (in the old style) and presents vanity name interfaces through it continues to work? What will happen to old applications that get a vanity name network interface given to them, such as "net0", but try to call kstat like this: kstat_lookup(kc, "net", 0, "net0") ...because the only way to derive the instance# is from the name and they expect the name to match the old naming convention.... Will old programs fail to work with kstats after UV? Darren
