>> The things won't work is that if you renamed bge0 to net0, and tries >> to lookup its kstat using kstat_lookup(kc, "net", 0, "net0"). > > > Right, this worries me. > I think this is an unavoidable problem once we have vanity naming though. > > While the APIs and ABIs are unchanged, software that works > today using libkstats may stop working after a "dladm rename". > > So, for example, I have S10U3 installed with package XYZ that > uses kstats() to get NIC information, I do an upgrade to S10Ux > with UV, dladm rename and things stop working. > > Hmm, the 20Q says that this project is targetting a minor release > of Solaris, so it will never go into a S10 update...so maybe this > change is ok? > Right. we are only targeting on Nevada as the current PSARC case. But we are considering and it is very possible that we will go back to PSARC and request to port UV to s10 update. There are certainly controversies - like this one, and the newly introduced dlpi_walk() (instead of the di_walk_minor()) to walk all interfaces.
> Are there documentation updates planned for kstat(1m) and > kstat_lookup(3kstat) that instruct people to use "link" for network > interfaces? > Thanks for reminding this. We will. But I am not sure whether it should go into the kstat(1M) manpage. Thanks - Cathy _______________________________________________ networking-discuss mailing list [email protected]
