http://defect.opensolaris.org/bz/show_bug.cgi?id=11385
--- Comment #3 from amaguire <alan.maguire at sun.com> 2009-09-18 14:17:37 UTC --- nwamcfg's current approach is to delete unneeded properties when a particular property changes (e.g. changing from a prioritized to a manual activation mode obsoletes the previously-required priority-group and priority-mode). That's a good approach to minimize configuration settings, but the problem is we lose information we might want in the future if we switch a property back to a previous value (e.g. going from prioritized to manual to prioritized activation-mode). It might be better to not delete properties in such cases, and instead use our tables of unneeded properties to inform the property listing and walk (i.e. if an NCU is manual, skip priority-mode and priority-group). Then if we switch back to prioritized later, we've got those values still set to what they were before. This means that a user can change or set the priority-group value by using "set" directly, but that the value does not take effect unless the NCU becomes prioritized (we could even use the prop table to print a warning like "property %s is not used when property %s has the value %s" in such cases). This approach is nice in that it's not "lossy", and we can minimize display of redundant properties. In the case of the enabled property, it's always added on creation for ENMs, NCUs and locations, so as long as we don't delete properties via nwamcfg, this general solution should address the bug filed. -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
