True, all true. The village I live in got Electricity in 1958, Mains sewarage in 1993, Gas in 1996, is a whole mine of copper out of ISDN range and on last enquiry, BT recommended a private Kilostream for my higher bandwidth requirements. We shall probably never get cable and the chances of ADSL are slim.
The issue is surely not really the libc5 and libc6 libraries themselves - a bit of fiddling with LD_LIBRARY_PATH and occasional wrapper scripts sorts that one out. And you can always find out which binaries require which library with ldd. In fact, I have a little perl auditer that tells you just which camp each executable is in.
The issue is really the run-time linker, and compatibility between glibc 2.0 and 2.1 that I can't find a satisfactory solution to, and no discussion I have yet seen has really resolved this one.
Slashdot Mirror
True, all true. The village I live in got
Electricity in 1958, Mains sewarage in 1993,
Gas in 1996, is a whole mine of copper out of
ISDN range and on last enquiry, BT recommended
a private Kilostream for my higher bandwidth
requirements. We shall probably never get cable
and the chances of ADSL are slim.
The issue is surely not really the libc5 and libc6 libraries themselves - a bit of fiddling with LD_LIBRARY_PATH and occasional wrapper scripts sorts that one out. And you can always find out which binaries require which library with ldd. In fact, I have a little perl auditer that tells you just which camp each executable is in.
The issue is really the run-time linker, and compatibility between glibc 2.0 and 2.1 that I can't find a satisfactory solution to, and no discussion I have yet seen has really resolved this one.