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.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
