> That's a very good point. > > If we had to change the name to promote something from public to private, > in addition to all the user-surprises this would create, > the upgrade procedure would have to do the task of purging the old name > from the dladm repository and inserting the new one.
The whole idea of private properties is that they are unstable across upgrades. The model you're currently proposing forces us to make a guarantee we can't keep: that we can transparently handle converting that driver-private property to a public one (including preserving the semantics). -- meem
