> I think hiding the physical name is right. Today we use often the > physical name to get information about the usable feature of a driver. > So if it's planned to get a GUI to show what interface is really behind > e.g. net0 a good (and maybe more useful) extension to that would be to > list the possible feature, that can be used with this interface: > - Autosensing with Speed > - tagged vlan ready > - vnic ready > - can use aggregates > - is ready for bandwidth management ...
We've been tackling this from two directions. One is to enhance dladm so that you can more easily learn about a link's capabilities (e.g., through the show-* commands and through the link property mechanism). The other is to unify the feature set -- and to that end, as part of the same putback that introduced vanity naming, a softmac shim was added that allows all Ethernet drivers to support VLANs, VNICs, aggregations, and bandwidth management (once available). -- meem
