Kyle McDonald writes: > Documenting (right in the admins) face why a config entery is the way it > is, or when wnad why it might be changed, right in the location where > they'll see it when they are changing it.
Indeed. But the uncool part here is that this thread is just recapitulating what was already discussed during the review of Greenline. That case _really_ needs to be opened up. > create new manifests in XML significantly raises that bar. I know SMF > can manage the older script methods, but as I understand it, that gives > reduced functionality, and the impression I've seen people have about it > is that it is only a temporary 'backward-compatibility' feature that > will disappear some day. What? That looks like FUD to me. The /etc/rc.* scripting interface is a stable part of the system, inherited from System V. I don't think it'd be sane at all to attempt to remove it or make it "disappear" in any way. If anyone involved with OpenSolaris (or Sun) were to try that, it wouldn't be by way of stealth, as you seem to be suggesting. It would be done openly, first with an ARC case that describes exactly how things transition in a compatible way, and then public notice to _all_ customers at least a year in advance of the change. I see no reason to generate unnecessary anxiety here. The people working on the system aren't _stupid_. > > The key to making useful software is simplicity and cleanliness of design. > > > +1 ... says the guy whose email is encoded in HTML. ;-} -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
