:: 03-Oct-1999 16:32 (Sunday) ::
Hi all,
As you may know, we have a glibc problem with x86 Linux clients. If
the client is statically linked with glibc 2.0, it can’t resolve
host names under glibc 2.1. And vice-versa.
Previously, we had ‘solved’ the problem by providing two clients, one
for glibc 2.0 and another for glibc 2.1. This is confusing for most
people.
I want you to beta-test another client. This v444 client was build
and linked against glibc 2.1.1 on a SuSE 6.2 system, but this time is
was dynamically linked. I think this should solve the problem, but I
need people to test this client to be sure.
I’m particularly interested in beta-testers on glibc *2.0*
systems. Tell me if it works on your machine or if it doesn’t, but
please include as much details as you can in either case.
Here’s the url :
http://nodezero.distributed.net/~remi/rc5des444-linux-x86-elf-mt-glibc2.tar.gz
and the GnuPG signature :
http://nodezero.distributed.net/~remi/rc5des444-linux-x86-elf-mt-glibc2.tar.gz.asc
Note to i386 & i486 users : You will see a slight drop in performance
because we can’t link the 386/486 self-modifying core in a dynamic
client. If you want the best performance, you should stick with the
443 client.
We will continue to include this 386/486 self-modifying core in future
a.out and libc5 clients.