Hi,
I don't think that pkg install should ever install to a new BE unless
specifically stated by a user. It could print an info that reboot is
required though.
Someone else proposed automatic restarts - well, please not. Definitely
not in enterprise. The problem with creating and installing to a new BE is
that all your crontabs, /etc files ,etc. will be reverted back to a
version from the moment package was installed and that could cause
unplesant surprise for many.
An extra option to install to a new be - fine, a default behaviour -
please no.
Same goes for image-update I think.
--
Robert Milkowski
http://milek.blogspot.com
On Mon, 15 Jun 2009, 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?
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
