On Tue, 16 Jun 2009, Bart Smaalders wrote:
Robert Milkowski wrote:
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.
We don't allow user to overwrite the components of the system that
require a reboot to activate. This prevents the various disasters
that have befallen people w/ a libc getting installed that won't
work on the currently running kernel, mismatched kernel modules in
the case of a power failure during patching, etc.
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.
The crontabs, /etc files, etc. date from the moment of package installation.
We can certainly fail an install if a new boot environment is required
and the appropriate flag isn't passed. I'm less included to do this
on image update, though, but we could change the current behavior if
people really wanted it; right now you always get a new boot environment
w/ image update.
I think I could live with image-update to always update into a new BE.
With pkg install while I understand the issues you mentioned still I don't
think this is a best approach to automatically create a new BE. Quite
often there are upgrades that require a reboot but actually not really so
and one can workaround it while OS is running.
Maybe if there is a package being installed and it requires a reboot it
should fail with an appropriate info that either extra option is required
so it installs to new BE and changes won't take effect until one reboots
to a new BE or an extra --force (or whatever) option is required to
install it anyway but an immediate reboot is highly recommended.
To be on a safe side perhaps a clone of current BE should be created and
once package installed succesfully the new BE would be destroyed? That way
if system reboots while install was hapenning it would boot from the old
(clone) OS automatically avoiding mismatch in kernel modules, etc...
?
--
Robert Milkowski
http://milek.blogspot.com
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
