On Sun, Nov 19, 2000 at 09:20:42PM -0500, Adam McKenna wrote:
>
> On Sun, Nov 19, 2000 at 05:47:39PM -0800, David Benfell wrote:
> > > Is there any reason you can't get a 2.2 SuSE RPM?
> >
> > Hmmm... They have an update to shlibs, which I think includes glibc.
> > They also have a few other updates that look relevant. In particular,
> > they have nssv1.
> >
> > So I installed all these, but glibc is still 2.1.3.
> >
> > >Is there
> > > any reason you particularly need 2.2?
> > >
> > I tend to go with latest versions. In stark contrast to the Debian
> > approach, I find latest versions less troublesome.
>
> I serioulsy suggest that you downgrade to your OS's latest supported glibc,
> unless there is a specific reason you need a later one. Building glibc from
> source is not for amateurs.
>
I think I've done just that:
benfell:~ # ls -al /lib/libc*
-rwxr-xr-x 1 root root 4070534 Sep 20 09:07 /lib/libc.so.6
lrwxrwxrwx 1 root root 17 Nov 14 10:39 /lib/libcom_err.so.2 ->
libcom_err.so.2.0
-rwxr-xr-x 1 root root 8133 Jul 29 07:33 /lib/libcom_err.so.2.0
-rwxr-xr-x 1 root root 61180 Sep 20 09:07 /lib/libcrypt.so.1
benfell:~ # rpm -qf /lib/libc.so.6
shlibs-2.1.3-163
This is the latest version of glibc that SuSE offers. "rpm -vf
/lib/libc.so.6 --verify" returns no output, so I presume all is well,
but just to be sure, I did "rpm -a --verify | less" and saw output
consistent with what I believe I've done to the system.
Next, I went looking for libresolv (note the before and after shots
separated by an updatedb):
benfell:/usr/local/src/qmail-1.03 # locate libresolv
/lib/libresolv.so.2
/usr/lib/libresolv.a
/usr/lib/libresolv.so
/usr/lib/libresolv_p.a
/usr/local/lib/libresolv-2.2.so
/usr/local/lib/libresolv.a
/usr/local/lib/libresolv.so
/usr/local/lib/libresolv.so.2
/usr/local/lib/libresolv_p.a
/usr/local/src/modutils-2.3.20/libresolv-dir.log
benfell:/usr/local/src/qmail-1.03 # updatedb ; locate libresolv
/lib/libresolv.so.2
/usr/lib/libresolv.a
/usr/lib/libresolv.so
/usr/lib/libresolv_p.a
/usr/local/src/libresolv.txt
/usr/local/src/modutils-2.3.20/libresolv-dir.log
/usr/local/src/qmail-1.03/libresolv.cc-log
/usr/local/src/qmail-1.03/locate-libresolv
The last few entries under /usr/local/src are text files containing
various output I've accumulated along the way through this thing.
> Also, I'm not sure what you mean by "the Debian approach". If you want to
> stay on the cutting edge, you can run the "unstable" version of debian, which
> is about as up to date as you can possibly be.
>
I think this is the wrong place for a religious war on Debian, but I
guess I did start it. I'll only say that from what I've seen, they
have lots of problems with their unstable branch. And they do warn
you about this. My approach has, so far, generated less difficulty,
mainly because I focus on packages for which there have been security
alerts. The solution for a security alert on "su" turns out to be
building against glibc 2.1.3 or higher. So I upgraded glibc (I think
this is a lot easier than it used to be) on my other systems and
rebuilt sh-utils successfully. Admittedly, in this case, it was
unnecessary to upgrade to glibc 2.2.
--
David Benfell
[EMAIL PROTECTED]
---
The grand leap of the whale up the Fall of Niagara is esteemed, by all
who have seen it, as one of the finest spectacles in nature.
-- Benjamin Franklin.
[from fortune]
PGP signature
