Enda O'Connor ( Sun Micro Systems Ireland) wrote: > Hi > How does IPS rid itself of the various scripts ( postinstall say ) that > SVR4 uses to provision your system post pkgadd, ie say add_drv or so on. >
We've just started along this path. We're basically breaking tasks performed in post-install scripts into two bunches: those that need to happen before boot/during install, and those that can wait after restart (whether service or OS). The tasks that are done immediately are called actions. Right now we have file, directory, link, hardlink, license, and driver actions. The latter action takes care of calling add_drv/update_drv as needed, for example. There will be more actions; clearly ones to take care of the *attr files, creating users/groups, etc are needed. We're also going to provide standard mechanisms to handle post-restart services; these are likely to be more flexible than the actions and are easier for everyone to code, since they only have to handle a single run-time context. One of the great benefits of eliminating scripting is that we can validate the behavior of the actions on zones; it should be possible to update disabled zones or cloned zone filesystems w/o security issues that require the use of scratch zones today. - Bart -- Bart Smaalders Solaris Kernel Performance [EMAIL PROTECTED] http://blogs.sun.com/barts _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
