linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
Cc: Keith Clayton <keith@claytons.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: glibc 2.1 -> 2.2 gotchas?
Date: Sat, 25 Aug 2001 17:35:10 +0200	[thread overview]
Message-ID: <3B87C5AE.2803935D@iiic.ethz.ch> (raw)
In-Reply-To: 01082511314308.15847@localhost.localdomain


"Kevin B. Hendricks" wrote:

> The other easy way to make this move is to simply upgrade to YDL 2, SuSE
> 7.1, Debian, Mandrake, etc. They are all glibc 2.2.X based and come with all
> of the other things that need to be upgraded since they are so old (Perl,
> etc).
>
> Upgrading them from glibc-2.2.1 to glibc 2.2.4 is easily done with rpm a few
> syncs and a restart.

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


--
Earthling Michel Dänzer (MrCooper)    \   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \        XFree86 and DRI project member

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

  reply	other threads:[~2001-08-25 15:35 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 [this message]
2001-08-25 15:42     ` Kevin B. Hendricks
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=3B87C5AE.2803935D@iiic.ethz.ch \
    --to=michdaen@iiic.ethz.ch \
    --cc=keith@claytons.org \
    --cc=khendricks@ivey.uwo.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).