On Wed, 9 Feb 2000, John Summerfield wrote:
> I have a RHL 5.0 system which I do NOT wish to update to 6.x. However, I
> would like to have glibc 2.1 on it; I'd like to run IBM's JDK on it and
> there's other software appearing that requires glibc 2.1.
>
> Is it sufficient to install these?
> -rw-r--r-- 1 summer 1311155 Feb 8 15:10 compat-glibc-5.2-2.0.7.2.i386
> .rpm
> -rw-r--r-- 1 summer 2006184 Feb 7 17:37 glibc-2.1.3-6.i386.rpm
> -rw-r--r-- 1 summer 2006184 Feb 7 17:39 glibc-devel-2.1.3-6.i386.rpm
> -rw-r--r-- 1 summer 1997992 Feb 7 17:41 glibc-profile-2.1.3-6.i386.rp
> m
>
> What recovery strategy should I adopt just in case this breaks something?
Install the compat-glibc one first. Then install your version of
glibc-2.1. You might find you have to relink/update your libraries if
they have C++ code in them and you want to link new applications with
them. Take a look at the glibc documentation, specifically in the FAQ
sections: 2.20, 3.20 might be of interest.
I would recommend staying away from glibc-2.1.3.*.rpms as they are not
really glibc 2.1.3, they are pre releases snapshots. Use the glibc
(2.1.2) released with RH 6.1 and you should be fine. If you use the 2.1.3
pre release stuff (which I believe Red Hat does not properly mark/name,
IMHO) you risk having binary incompatible stuff. As was seen when the
rlimit patches were removed from pre 3 (on ix86, they will be gone in the
next pre relase on ARM).
As for recovery (which shouldn't be necessary, it will all work the first
time :) ), make certain you have a static version of rpm around, any
current release of rpm 3.x should do. And get a static shell, sash would
do. Keep a copy of the old glibc 2.0 rpms on your root partition. And
if things get really broken you can always recover with something similar
to the following to lilo:
<label> init=/bin/sash
/usr/i386-glibc20-linux/lib/ld-2.0.7.so mount -o remount,rw -n /
You might have to set the ld preload path for libc, forget about this
part..
(fight with mount to remount in read/write mode (or keep a static copy
around)
Then downgrade your version of glibc
> Should I be worried that two of these are the same size?
Yes, they look incomplete (they should be much larger). Try
rpm --checksig --nopgp <rpm name...>
[Note: Your light year travel may vary]
-Rms
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
