> What updates in Solaris require a reboot?
I've been spoiled by using the Sun Update manager, so I just reboot when
it tells me I need to.
I think Ian's question is what types of updates require a reboot or what
the criteria was for deciding that as opposed to implying that he has
never ran / used Solaris.
I expect that, if the various consolidations and such were re-arranged,
one could probably coerce a solaris host to not require reboots for most
anything but kernel updates.
The current situation - where you have massive patches like 118833-36 (a
recent 'kernel' patch) that update the kernel plus big hunks of userland -
is rather unsatisfactory.
I understand the need to be somewhat atomic - hey, you don't want to
upgrade the kernel and then have one of the REQUIRED utility upgrades fail
to patch onto the system: crashes would result, frequently - but I expect
that this is one of the things that Indiana should focus on fixing,
posthaste.
Can we safely assume that increasing the end-user's ability to smoothly
upgrade - piecewise, if possible - is a desirable outcome of Indiana?
I think that a lot of the potential problems incurred by slicing up larger
patches can be taken care of by careful testing and explicit requirements
for particular versions of packages.... zfs rollback could make this
testing quite lovely for developers.
--e
_______________________________________________
indiana-discuss mailing list
[email protected]
http://opensolaris.org/mailman/listinfo/indiana-discuss
