> The escape clause in IPS is to install a one-shot SMF > service that can > do whatever you want, like assemble a config file > from multiple bits.
To the best of my knowledge and belief, as of right now, SMF provides no capability for a one time run, so getting post-installation code to run via SMF is tricky, with one svcadm refresh, and one svccfg delete. Is it really practical to take the "no scripting zone" design so far as to force people to resort to "backdoors" and hacks via SMF, which SMF doesn't even rightly support yet? I mean, if I have to use SMF to do postinstall, I clearly have the need to execute code upon software installation and removal. Why refuse to give me capability to do that in the packaging system? -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
