glibc 2.1 -> 2.2 gotchas?

glibc 2.1 -> 2.2 gotchas?

[Keith Clayton]

Hi all,

I'm considering moving from glibc 2.1.3 to 2.2.4  Any known problems
with the move to 2.2, apps that break, etc.

I'm hoping to minimize any surprises


Thanks
Keith


--
<><><><><><><><><><><><>
Keith Clayton
keith@claytons.org

"If you don't trust me with your source code,
            why should I trust you with my computer?"

GPG key: http://home.pacbell.net/clay-ton/keith_public_key.html
         http://www.keyserver.net

GPG fingerprint: 33FF 1D80 4562 1600 4BAB  5018 BCB7 635C B0CC 99EE


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

Re: glibc 2.1 -> 2.2 gotchas?

[Kevin B. Hendricks]

Hi Keith,

If you are using an RPM based distribution, please be careful.  When I tried
to do the upgrade manually awhile back I ran into trouble with many of the
new rpms being usable in RPM 4 format only and not working under RPM 3.

If I were you I would rebuild glibc 2.2.4 from a source rpm (from Franz) and
run make check first just to make sure all is well.  I would then focus on
building RPM 4 and then try to convert your rpm database over from RPM 3 to
RPM 4.o and then continue upgrading pieces.

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.

Hope this helps,

Kevin

On Saturday 25 August 2001 10:55, Keith Clayton wrote:
> Hi all,
>
> I'm considering moving from glibc 2.1.3 to 2.2.4  Any known problems
> with the move to 2.2, apps that break, etc.
>
> I'm hoping to minimize any surprises
>
>
> Thanks
> Keith
>
>
> --
> <><><><><><><><><><><><>
> Keith Clayton
> keith@claytons.org
>
> "If you don't trust me with your source code,
>             why should I trust you with my computer?"
>
> GPG key: http://home.pacbell.net/clay-ton/keith_public_key.html
>          http://www.keyserver.net
>
> GPG fingerprint: 33FF 1D80 4562 1600 4BAB  5018 BCB7 635C B0CC 99EE
>
>

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

Re: glibc 2.1 -> 2.2 gotchas?

[Michel Dänzer]

"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/

Re: 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/

Re: glibc 2.1 -> 2.2 gotchas?

[Kaoru Fukui]

From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>


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

it's no needs.
Please read glibc's FAQ  which has glibc source

I have here also at

 ftp://ftp.linuxppc.org/users/kfukui/glibc-2.2.x-room/RPMS/FAQ.glibc-2.2.3

Kaoru


------------ glibc-2.2.3.FAQ (only 2.32)--------------------
2.32.	What has do be done when upgrading to glibc 2.2?

{AJ} The upgrade to glibc 2.2 should run smoothly, there's in general no
need to recompile programs or libraries.  Nevertheless, some changes might
be needed after upgrading:
- The utmp daemon has been removed and is not supported by glibc anymore.
  If it has been in use, it should be switched off.
- Programs using IPv6 have to be recompiled due to incompatible changes in
  sockaddr_in6 by the IPv6 working group.
- The Berkeley db libraries have been removed (for details see question 2.31).
- The format of the locale files has changed, all locales should be
  regenerated with localedef.  All statically linked applications which use
  i18n should be recompiled, otherwise they'll not be localized.
- glibc comes with a number of new applications.  For example ldconfig has
  been implemented for glibc, the libc5 version of ldconfig is not needed
  anymore.
- There's no more K&R compatibility in the glibc headers.  The GNU C library
  requires a C compiler that handles especially prototypes correctly.
  Especially gcc -traditional will not work with glibc headers.

Please read also the NEWS file which is the authoritative source for this
and gives more details for some topics.
---------------------------------------------------------


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

Re: glibc 2.1 -> 2.2 gotchas?

[Kevin B. Hendricks]

Hi

> it's no needs.
> Please read glibc's FAQ  which has glibc source
>
> I have here also at
>
>  ftp://ftp.linuxppc.org/users/kfukui/glibc-2.2.x-room/RPMS/FAQ.glibc-2.2.3

All I saw here was for installing after building from source code.  I did not
see anything about installing using a package manager.

Perhaps my use of "ldconfig -v; sync; sync; shutdown -r now" comes from the
days when rpm was not always staticaly linked with libc?

What I recommend won't hurt and can certainly help flush older shared
libraries out of memory.

It is of-course Keith's choice but I still recommend it.

Kevin

(ps. you might want to check out RedHat's instructions for using rpm to
upgrade glibc, that used to be on their site.  That is what I based my
procedure on a long time ago (around mklinux rel 1).

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

Re: glibc 2.1 -> 2.2 gotchas?

[Kaoru Fukui]

I suggest that Don't compile glibc yourself,because current glibc,gcc-2.95.4
or gcc-3.0.1 need some patches.

I used these patches into my glibc package.

Kaoru

PS: Debian developper's Ben colins know it well
 or see glibc,gcc mail list.


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

Re: glibc 2.1 -> 2.2 gotchas?

[Michel Dänzer]

"Kevin B. Hendricks" wrote:

> > it's no needs.
> > Please read glibc's FAQ  which has glibc source
> >
> > I have here also at
> >
> >  ftp://ftp.linuxppc.org/users/kfukui/glibc-2.2.x-room/RPMS/FAQ.glibc-2.2.3
>
> All I saw here was for installing after building from source code.  I did
> not see anything about installing using a package manager.
>
> Perhaps my use of "ldconfig -v; sync; sync; shutdown -r now" comes from the
> days when rpm was not always staticaly linked with libc?

dpkg still isn't.

> What I recommend won't hurt and can certainly help flush older shared
> libraries out of memory.

The point is probably that in the Debian packages, the maintainer scripts take
care of the necessary steps, so the user doesn't have to.


--
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/

Re: glibc 2.1 -> 2.2 gotchas?

[Tom Rini]

On Sun, Aug 26, 2001 at 12:31:37AM +0200, Michel D?nzer wrote:

> > What I recommend won't hurt and can certainly help flush older shared
> > libraries out of memory.
>
> The point is probably that in the Debian packages, the maintainer scripts take
> care of the necessary steps, so the user doesn't have to.

This always got me tho...  If a program is already running, how do you
make it stop using the old libraries?  If 'restarting' /sbin/init makes it
reload, I'll take your word at it.  But what about all of the other apps that
happen to be running?  The bash session I happen to be doing this upgrade
from.  Or X (yes, in an ideal world, you goto single user to do this
anyhow.. :))

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

Re: glibc 2.1 -> 2.2 gotchas?

[Daniel Jacobowitz]

On Sat, Aug 25, 2001 at 03:42:33PM -0700, Tom Rini wrote:
>
> On Sun, Aug 26, 2001 at 12:31:37AM +0200, Michel D?nzer wrote:
>
> > > What I recommend won't hurt and can certainly help flush older shared
> > > libraries out of memory.
> >
> > The point is probably that in the Debian packages, the maintainer scripts take
> > care of the necessary steps, so the user doesn't have to.
>
> This always got me tho...  If a program is already running, how do you
> make it stop using the old libraries?  If 'restarting' /sbin/init makes it
> reload, I'll take your word at it.  But what about all of the other apps that
> happen to be running?  The bash session I happen to be doing this upgrade
> from.  Or X (yes, in an ideal world, you goto single user to do this
> anyhow.. :))

They keep running with the old libc.  No big deal, really :)  The RAM
will basically not be reclaimed until after you reboot.

--
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

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

Re: glibc 2.1 -> 2.2 gotchas?

[Tom Rini]

On Sat, Aug 25, 2001 at 03:54:17PM -0700, Daniel Jacobowitz wrote:
>
> On Sat, Aug 25, 2001 at 03:42:33PM -0700, Tom Rini wrote:
> >
> > On Sun, Aug 26, 2001 at 12:31:37AM +0200, Michel D?nzer wrote:
> >
> > > > What I recommend won't hurt and can certainly help flush older shared
> > > > libraries out of memory.
> > >
> > > The point is probably that in the Debian packages, the maintainer scripts take
> > > care of the necessary steps, so the user doesn't have to.
> >
> > This always got me tho...  If a program is already running, how do you
> > make it stop using the old libraries?  If 'restarting' /sbin/init makes it
> > reload, I'll take your word at it.  But what about all of the other apps that
> > happen to be running?  The bash session I happen to be doing this upgrade
> > from.  Or X (yes, in an ideal world, you goto single user to do this
> > anyhow.. :))
>
> They keep running with the old libc.  No big deal, really :)  The RAM
> will basically not be reclaimed until after you reboot.

That's sorta what I figured.  So on debian certain services get restarted
so that new children are sane, yes?

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

Re: glibc 2.1 -> 2.2 gotchas?

[Daniel Jacobowitz]

On Sat, Aug 25, 2001 at 09:36:29PM -0700, Tom Rini wrote:
>
> On Sat, Aug 25, 2001 at 03:54:17PM -0700, Daniel Jacobowitz wrote:
> >
> > On Sat, Aug 25, 2001 at 03:42:33PM -0700, Tom Rini wrote:
> > >
> > > On Sun, Aug 26, 2001 at 12:31:37AM +0200, Michel D?nzer wrote:
> > >
> > > > > What I recommend won't hurt and can certainly help flush older shared
> > > > > libraries out of memory.
> > > >
> > > > The point is probably that in the Debian packages, the maintainer scripts take
> > > > care of the necessary steps, so the user doesn't have to.
> > >
> > > This always got me tho...  If a program is already running, how do you
> > > make it stop using the old libraries?  If 'restarting' /sbin/init makes it
> > > reload, I'll take your word at it.  But what about all of the other apps that
> > > happen to be running?  The bash session I happen to be doing this upgrade
> > > from.  Or X (yes, in an ideal world, you goto single user to do this
> > > anyhow.. :))
> >
> > They keep running with the old libc.  No big deal, really :)  The RAM
> > will basically not be reclaimed until after you reboot.
>
> That's sorta what I figured.  So on debian certain services get restarted
> so that new children are sane, yes?

Yes, precisely.  Most of the network daemons that use NSS need to be
restarted, because of how NSS is loaded.

--
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

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

Re: glibc 2.1 -> 2.2 gotchas?

[Keith Clayton]

Thanks to all who responded to my query . . you guys are great.

I was gone all day yesterday and woke up to find my inbox full of great
info!

Looks like I've got some work cut out for me no matter which route I
head.  Guess my labor day weekend will live up to its name ;)

Thanks again . . this gives me lots to chew on

Cheers,
Keith

On 25 Aug 2001 11:31:43 -0400, (null) wrote:
> Hi Keith,
>
> If you are using an RPM based distribution, please be careful.  When I tried
> to do the upgrade manually awhile back I ran into trouble with many of the
> new rpms being usable in RPM 4 format only and not working under RPM 3.
>
> If I were you I would rebuild glibc 2.2.4 from a source rpm (from Franz) and
> run make check first just to make sure all is well.  I would then focus on
> building RPM 4 and then try to convert your rpm database over from RPM 3 to
> RPM 4.o and then continue upgrading pieces.
>
> 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.
>
> Hope this helps,
>
> Kevin
>
> On Saturday 25 August 2001 10:55, Keith Clayton wrote:
> > Hi all,
> >
> > I'm considering moving from glibc 2.1.3 to 2.2.4  Any known problems
> > with the move to 2.2, apps that break, etc.
> >
> > I'm hoping to minimize any surprises
> >
> >
> > Thanks
> > Keith
> >
> >
> > --
> > <><><><><><><><><><><><>
> > Keith Clayton
> > keith@claytons.org
> >
> > "If you don't trust me with your source code,
> >             why should I trust you with my computer?"
> >
> > GPG key: http://home.pacbell.net/clay-ton/keith_public_key.html
> >          http://www.keyserver.net
> >
> > GPG fingerprint: 33FF 1D80 4562 1600 4BAB  5018 BCB7 635C B0CC 99EE
> >
> >
--
<><><><><><><><><><><><>
Keith Clayton
keith@claytons.org

"If you don't trust me with your source code,
            why should I trust you with my computer?"

GPG key: http://home.pacbell.net/clay-ton/keith_public_key.html
         http://www.keyserver.net

GPG fingerprint: 33FF 1D80 4562 1600 4BAB  5018 BCB7 635C B0CC 99EE


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