From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: "Michel Dänzer" <michdaen@iiic.ethz.ch>
Cc: Keith Clayton <keith@claytons.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: glibc 2.1 -> 2.2 gotchas?
Date: Sat, 25 Aug 2001 11:42:45 -0400 [thread overview]
Message-ID: <01082511424509.15847@localhost.localdomain> (raw)
In-Reply-To: <3B87C5AE.2803935D@iiic.ethz.ch>
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/
next prev parent reply other threads:[~2001-08-25 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-25 14:55 glibc 2.1 -> 2.2 gotchas? Keith Clayton
2001-08-25 15:31 ` Kevin B. Hendricks
2001-08-25 15:35 ` Michel Dänzer
2001-08-25 15:42 ` Kevin B. Hendricks [this message]
2001-08-25 15:55 ` Kaoru Fukui
2001-08-25 17:44 ` Kevin B. Hendricks
2001-08-25 18:06 ` Kaoru Fukui
2001-08-25 22:31 ` Michel Dänzer
2001-08-25 22:42 ` Tom Rini
2001-08-25 22:54 ` Daniel Jacobowitz
2001-08-26 4:36 ` Tom Rini
2001-08-29 21:08 ` Daniel Jacobowitz
2001-08-26 14:52 ` Keith Clayton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01082511424509.15847@localhost.localdomain \
--to=khendricks@ivey.uwo.ca \
--cc=keith@claytons.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michdaen@iiic.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).