Casper.Dik at sun.com wrote: > The Registry model is NOT one to aspire to.
I have to just completely disagree there. I think there are numerous advantages to such a model, and very few disadvantages. > For one I strongly dislike the fact that I never have an idea > what is the current property and which would be the property value > on boot; clearly they are different at times. First, I'd personally say that they should _not_ be different. However, given that people seem to insist that they want to allow the two to be different, I agree that there should be a way to see both and to see the differences. Having both available through centralized interfaces seems like the right answer to that question. Having them, especially the runtime settings, available only through per-service interfaces would make it practically impossible to build any system-wide tools to display those settings and differences. (Granted, I don't think SMF currently has any way to show runtime settings, but they could be worked in. That would require further application cooperation. However, previous configuration technology offers _less_ visibility.) > Secondly, SMF has already proven to me to be too fragile [...] I have no opinion on its fragility and agree that it must _not_ be fragile. I see no technical reason that it must be fragile.
