On Fri, Dec 18, 2009 at 3:36 AM, Volker A. Brandt <v...@bb-c.de> wrote: >> What's needed is a supported mechanism to make it >> easy to do it right. > > +999999999999999999999999999999999999999
When Stephen and Bart and company started talking about IPS leveraging SMF, I suggested that it might be possible to keep the SVR4 pkg pre/post install/remove script idea, add the "usual" SMF start/stop/restart bits and automatically put the whole shebang into the SMF framework at install time. The response was "we don't do scripting in pkgs - they should write their own SMF stuff themselves".... I don't see leveraging SMF as a hack - heck, to me, inventing a 1-off meta language to be used just for pkg scripts seems much more limiting and hackish than leveraging SMF.... Maybe SMF needs to evolve the idea of "svcadm install/remove service" so it would have a semantic place to put the pre/post install/remove scripts, or maybe the first "enable" would simply notice that the service had not yet run its install script; the result would be what people are asking for without the problems associated with "wrong context". -John _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
