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.
Not for the modifiable files though they date from the moment of the
snapshot taken to create the new be. With the legacy live_upgrade(5)
system there is a copy process when the currently running BE shutsdown
to ensure that any important files that were modified after the BE was
cloned are copied over to the new BE that is going to be active.
The new BE management doesn't have that step.
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 getting a new BE with image-update should be the default but if
you want to get out of it you can. The only case I can think of where
you might not want this is if the only updates are "security fixes" but
I'd really not want to special case that because they aren't special
from a packaging view point they are just important (to some people) bug
fixes.
--
Darren J Moffat
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
