glibc 2.1 -> 2.2 gotchas?

[Kevin B. Hendricks]

Hi,

> No restart needed with Debian, the glibc upgrade will just ask if it should
> restart a few services.

You are brave!  I always do a ldconfig -v; sync; sync; shutdown -r now and
invariably I see inodes that need repairing after a glibc update.

Perhaps the Debian package manager is better?  But I can't see how it can
really switch running processes to the new glibc so it must keep both until
the next reboot?

It may be extreme overkill but I will still do a ldconfig -v (so that all
versioned libraries symlinks are updated properly); sync; sync; shutdown-r
now immediately after upgrading glibc.

I guess I am just old and paranoid!

Take care,

Kevin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/