On Mon 15 Jun 2009 at 08:03PM, Bart Smaalders wrote:
>
> I'm looking at making pkg install and pkg image-update do the
> right thing wrt boot environments. We're already tagging files that
> should require a reboot if modified in the live system w/
> the reboot_needed tag. What I'm considering doing is making
> pkg install and pkg image-update use this as the deciding
> factor as to whether or not to create a new boot environment.
> This way, a security update that only has a new version of
> firefox won't create a new BE during image-update, but
> pkg install ent...@116 would.
>
> Do people want an option to force both pkg install and pkg image-update
> to always create a new BE? How about one to cause the operation
> to fail if a new BE is required?
So something like this?
--create-be=as-needed (or "auto")
--create-be=yes (or "always")
--create-be=no (or "never")
Perhaps (create-be=no would, as you say, fail if a reboot was
needed). I presume pkg uninstall and fix would also get these
options.
One thing I think is missing is something with which we can
do basic automation. For example, it'd be nice to be be able
to know if pkg created a BE-- and for example, if so, to trigger (or
schedule) a reboot. I could see that being very useful in enterprise
environments. There's no real way to know that today without analyzing
the output of the command.
-dp
--
Daniel Price, Solaris Kernel Engineering http://blogs.sun.com/dp
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
