On Mon, 2008-02-04 at 20:29 -0500, Sebastien Roy wrote: > John Fischer wrote: > > Instead, JDS in Nevada uses postrun for running these programs. > > Postrun generalizes the above idea by putting the complex > > script into a shared script (postrun itself) and using a > > single smf service for all first-boot commands. > > When can consumers of postrun expect their scripts to be run at first > boot? My question hints at a potential limitation of postrun for > packages that expect their changes to have taken effect very early in > boot (earlier than the postrun SMF service is started). It may be > worthwhile to call out this limitation to set appropriate expectations.
The dependencies are svc:/system/filesystem/local and svc:/system/sysidtool:system. So that's the earliest they will be run. At the other end, gnome-session waits for all postrun scripts in the JDS_wait class to complete before the session is started. (A progress bar is displayed, the label is something like 'completing post installation confirugation'.). The current consumers are at the desktop level (note that postrun is JDS Consolidation Private), so that should be early enough but not too early for the installation of desktop components. I agree this could be a limitation if postrun was used outside the desktop stack. Laca
