We currently have 3 finalizer modules that create the bootroot. bootroot_initialize: creates and populates the bootroot bootroot_configure: Does configuration on the bootroot. This includes creating the smf repository. bootroot_archive: unmount and lofiadm -d the bootroot areas and compressing.
After this the DC does post boot root modifications to the pkg_image area and creates the iso's and usb's. Unfortunately, it is impossible to rollback to the bootroot checkpoints after the archive step. i.e. after the microroot areas have been unmounted and lofiadm -d. Even if you go about recreating the mounts. Checkpointing works fine if you have not done that step. It appears we have some options on what we can do. 1) Move the ti_release_target to the end of the build. I don't even know if this is possible and all it does is narrow the window of when checkpointing the bootroot doesn't work. 2) During initialize and configure check to see if the mounts are there and if so rollback and everything works. If they are not there, display an error message telling the user they need to resume from the bootroot_initialize step. I don't see option 1 as really helping much and will proceed with option 2. Other solutions are welcome. Jean
