On Fri, Sep 04, 2009 at 12:31:15PM -0400, Rishi Srivatsavai wrote: > We need an option (3) where our new SMF service (immediately on > re-configure boot after a system upgrade) can run with fileystem > mounted read-write and before datalink-management service runs.
You're over-constraining this option (3). In IPS parlance your software needs to be self-assembling. In this case _you_ think that means "some config file must be updated" but "so early in boot that / is read-only", followed by "woe are we". But perhaps it'd be possible to fix the software that _reads_ that config file so it can deal with the pre-upgrade config file. If you can do that then you'd have "self-assembling" software and no dependencies on SMF. You might still want to have a one-shot service to upgrade the config file (when / is rw). And you might need a flag whose absence indicates that the config file has not yet been fixed. But those are details. Pre-IPS we all tended to view upgrade work as packaging work, and to think that writing upgrade code in C in daemons and utilities was a bad idea. It still may be the right view, but when the other tools that IPS & SMF give you won't cut it, then that's what you're left with. > Looks like this option (3) is possible after the Early Manifest Import > project for SMF is available. So for now we propose the following > as a short-term solution: Let dladm fail to bring-up VLANs with VID 1 > and we document this change and resolution in the release notes. Once > EMI integrates we will create a service to handle this update. Yes, IMO that's the most expedient option. Nico --
