Re: [cobalt-users] quick upgrade patch method?

[Jeff Lasman <blists@xxxxxxxxxxxxx>]

On Monday 16 February 2004 02:02 pm, Zeffie wrote:

> well I can say that I have done several in a similar way...

We automate it as well Zeffie, for lots of systems.

> I think many of the updates that ask for a
> reboot are just doing a more clear cut "we know it's running now"...
> as far as I know there are no "run after boot scripts"

We do reboots after kernel updates, too.  And after library updates as 
well, and then at the end of the upgrade cycle (when there are lots of 
updates going on at once).

I agree that Sun Cobalt does a lot more rebooting than necessary, but 
since I don't study each of their update packages I can't give you any 
more details than you've got.

I suppose a study of any particular package would indicate if a reboot 
was really required...

But the only reasons I can think of to restart any linux boxes rather 
than affected services would be kernel updates and library updates.

Jeff
-- 
Jeff Lasman, nobaloney.net, P. O. Box 52672, Riverside, CA  92517 US
Professional Internet Services & Support / Consulting / Colocation
Our blists address used on lists is for list email only
Phone +1 909 324-9706, or see: "http://www.nobaloney.net/contactus.html";