Thorsten Kukuk wrote:
glibc1 is glibc 1.0.x, and libc5 based on it. glibc2 is the new glibc, aka libc.so.6 under Linux. The latest public release of glibc 2 is 2.0.6. There are some 2.0.7preX, but the real bug fixes are only in the CVS archive. Since glibc 2.1 should be released this days, the glibc-maintainer will not make a public 2.0.7.
Lets say, Suse comes with glibc2.07, or whatever the latest snapshot is. When glibc2.1 comes out, will it be a simple matter of "copying over" the older glibc files? Is everything going to start being backward-compatible? Or will the shared libs from 2.06 need to be kept for software written with 2.06 in mind. In other words, are we going to have only 1 libc.so.6, or will there be libc.so.6, and libc.so.6.1, etc, etc. Also, why won't some elf executables that I made under Redhat 5.2, execute on SuSe5.3, even though I have installed the Shared Lib6 rpm on SuSE? Why aren't they totally compatible? If it's too complicated, just forget answering this. I'm fully resigned to waiting for 6.0 to come, and see how things go. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>