--- "Richard L. Hamilton" <[EMAIL PROTECTED]> wrote:

> > That is fine for installation of new OS. I do not
> see
> > how that would beat thousands of systems grabbing
> the
> > latest package, updating and then continue to run
> as
> > normal whereas flar would require those systems to
> > reboot for a mere update.
> 
> While I think a lot of current Solaris patch READMEs
> simply call for
> a reboot rather than bothering to explain under what
> conditions
> it might be necessary, I also suspect that anyone
> who believes that
> almost arbitrary updates can be done without any
> need for a reboot
> is sadly misguided.  Even if a reboot wouldn't be
> needed to prevent
> a crash, I think certain updates are best done in
> something like
> single-user mode, so that it's assured that an
> application is using either
> entirely the pre-update environment, or the
> post-update environment,
> but not some possibly unstable mix of the two.  Yes,
> I know that in most
> isolated cases of a lib or something being in use,
> it's not a problem as long
> as files being updated are not overwritten, but are
> replaced atomically
> (load new version under derived name, and then
> rename it into place).  But
> AFAIK, there's no way to simultaneously replace
> multiple files atomically,
> which means there's no way to have a totally clean
> cutover in case for
> example libs have private interfaces between one
> another, or a lib
> has a set of run-time-loaded plugins, or the like). 
> And that's just a
> simple example.

I imagine we have a very different view of 'updates'
due to the differences in tools, the contents of those
updates and the way they are done. On the Linux side
of things, no reboots are needed at all save for new
kernel installations and only if you want to run that
spanking new updated kernel (probably likely if it has
security fixes or a bugfix you want).

Send instant messages to your online friends http://uk.messenger.yahoo.com 
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to