Gary, > And we should question every addition to /etc/*. New /etc/* files > need justification as specified in the ARC SMF policy.
I can certain appreciate the policy with respect to the bits of software that are represent of core part of Solaris but I don't agree it should apply generally with the large number of FOSS components that are being merely aggregated from upstream communities. It's important that the familiarity of these components across multiple OS platforms be maintained in *most* cases. There are, of course, exceptions here - putting executables in /etc seems wrong in all cases - but for the most part, I don't see an issue with new components delivering files under /etc unless they're interfering with other components (/etc/security might fall into this case but that didn't apply with this particular case.) I do agree with Jyri that it would be helpful to note the pathnames of the files being dropped into the file system even if they're not interfaces themselves. Even just a sentence that says the project consists of Python files delivered in the standard /usr/lib/python2.4/vendor-packages helps. dsc
