As I mentioned in my comments on this bug (http://defect.opensolaris.org/bz/show_bug.cgi?id=11082), I'm concerned that the enable-svcs and disable-svcs properties are likely to cause confusion and inconsistent behavior for people who try to use them. We don't track the state of the service prior to activation of the location, so we don't know how to restore that state when the location is deactivated.
Furthermore, users can get really similar functionality by creating ENMs that are dependent on the location. So we have a feature that's both somewhat redundant, and also difficult to implement in a way that will result in consistent, predictable behavior. That's not a good combination. I also think that in the future, as locations become more smf-connected, adding this functionality, and making it work well, will be much easier. So as much as I hate to make a change like this at this stage of the game, I really think the thing to do right now is remove this feature. I think that action is the most likely to result in greater stability for phase 1. Thoughts? -renee
