Dave Miner wrote: > Tim Knitter wrote: >> >> Dave Miner wrote: >>> Tim Knitter wrote: >>>> IPSers, >>>> >>>> For the opensolaris May release the install team is integrating snap >>> upgrade which is comprised of a Boot Environment CLI, a C library to >>> manage the BE's and a glue library to convert Python calls -> C for >>> interfacing with the C library. This is the Live Upgrade replacement. >>> See http://www.opensolaris.org/os/project/caiman/Snap_Upgrade for more >>> details. >>>> My proposal is to modify pkg(1) to make use of the Snap Upgrade >>>> tools. >>> So I am in the process of modifying pkg(1) to support the following >>> scenarios: >>> >>>> pkg image_update >>>> - Take a snapshot of the BE before the attempted update >>>> - Clone and mount the snapshot >>>> - Update the clone >>>> - If there are update errors: >>>> ~ destroy the snapshot, unmount and destroy clone >>>> leaving the live BE untouched. >>> I'm wondering if we should have an option to leave the clone mounted >>> and in place, though, for diagnostic purposes. >>> >> >> Yes that is a good idea. Were you thinking of a private or public >> option? Or maybe it should be the default behavior for the May release. >> > > I hate private options, so that would be my last choice. I'd favor it > being the default, because having to re-run a significant task in order > to get to a diagnosable state seems to lead to problems not being > diagnosed.
OK so if image-update fails on a live system the failed clone will be left around for inspection by default, no option needed. Tim > > Dave _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
