On 22/04/2010 02:16, Bart Smaalders wrote:
As of 2010/03, we always create new boot environments
when doing an image-update, and never do so for
install, instead failing the operation should an action
tagged w/ reboot-needed be affected. We also always
create new boot environments for change-variant and
change-facet operations, and never for fix.
This needs work.
Instead, I'd like to propose the following:
1) We support the creation of a new optional backup
boot environment before executing the operation
on the live image. Non-live images can easily
use snapshots for this; this option would have
no effect in the case that the operation creates
a new BE.
So can a Live image, if there is ever a need to rollback
to the point of the install a clone can be created at
that point (a very recent bug fix actually made it possible to boot from
the snapshot too but that is beyond what I think should be
attempted here as there are much bigger issues with that).
However creating a clone it cheap enough so sticking with that
for live images makes sense.
2) All image-modifying operations on a live image
would create a new boot environment only if needed.
This behavior could be altered via command line flags
to always create a new boot environment or to never
create one, failing instead if the operation needs
one.
Seems reasonable. I feel like I'm both gaining install flexibility and
losing safety with this change but with the CLI options I have choice.
So looks reasonable all in. What I'm struggling with at the moment is
wither this will make upgrades easier to understand or not - I think it
does.
--
Darren J Moffat
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
