[osol-discuss] Arbitrary scripting for post-install configuration

[Scott Rotondo]

Peter Tribble wrote:
>>> To configure 'anything' requires essentially arbitrary scripting. First you
>>> tell us that arbitrary scripting will never be allowed, then you tell us that
>>> it's necessary, but we all have to implement our own mechanisms to
>>> get it.

Shawn Walker wrote:
>> No, we've told you that you have to move your scripting out of 
>> installation context where it only needlessly complicates the job of 
>> package management.

Yes, I think there is no getting away from arbitrary scripting, though I 
understand the desire to move it out of the installation context.

Casper.Dik at Sun.COM wrote:
> And instead we run it on *every boot* which makes booting the system slower
> and maintenance of a installed system harder?
> 
> (Much of what "svcs" today prints is "scripts runs at boot which would
> really needed to be run once when the system/package is installed"; that
> alone makes it a lot harder to find out all the services running as
> you can't see the forest for the trees)
> 
> We could probably fix it by making "svcs" only print services with running 
> processes; the other services are typically not of interest.
> 

It seems to me that OpenSolaris needs a single built-in service that 
runs these one-shot scripts for post-install configuration. Then every 
package could use it by delivering its script files to a predetermined 
directory.

We currently have 91 class action scripts used by packages in ON Nevada. 
I don't think we want to see the same basic functionality implemented 
dozens and dozens of times.

	Scott

-- 
Scott Rotondo
Principal Engineer, Solaris Security Technologies
President, Trusted Computing Group
Phone/FAX: +1 408 850 3655 (Internal x68278)