> > I always update my IA32 systems while they're live, but I think it can go a
> wry.
> > Think of something starting up while you're updating glibc - it could get s
> ome
> > old versions of libraries and some new.
>
> The application will be loading backward compatible libraries


glibc may not be the best example; I chose it simply because everything uses it.
I can imagine that a bug-fix in something might prevent complete compatibility.

Call me Doubting John if you wish. It's true I've never had a problem, but I've
never had a critical workload to worry over either.

>
> > Additionally, for some packages there can be configuration-file changes. As
>  so
> > often, it depends.
> >
> > Taking it out of service is always safe, but not always essential.
>
> I work on the rule of scheduling potential downtime but hoping its not
> needed. I've done 7.2->7.3 updates on x86 without downtime (barring kernel)

I did extensive upgrades on 4.2 too, remotely and without a problem.
--
Cheers
John Summerfield

Microsoft's most solid OS: http://www.geocities.com/rcwoolley/

Note: mail delivered to me is deemed to be intended for me, for my disposition.

==============================
If you don't like being told you're wrong,
        be right!

Reply via email to