On Sun, Sep 28, 2008 at 02:48:04PM +0900, Izumi Tsutsui wrote: > BTW, libpthread major wasn't bumped on SA to 1:1 migration. > > This means libpthread APIs have not been changed > while SA syscalls have been removed. This is not news. > Is there any reason why "thousand binaries" have to be recompiled > even if libc.so and libpthread.so will also be updated with > the new post SA kernel? The trick is, because of some other change in another library without a major bump, there is a third binary that you need to update. (Yes, that's very wrong. Changing it back, however, would mean removing symbols from libc. Even worse. We could bump libcrypt's major now, though.) > Or, does the "compatibility problem" only affect chroot environments > where any base libraries must not be updated? Yes. But all of that has already been discussed, you know. You could have read the archives. The thing is, system administrators, which is our target in this discussion, please keep that in mind, tend to be rather conservative when it comes to upgrading machines. The more conservative they can be, the happier they will be. -- Quentin Garnier - cube%cubidou.net@localhost - cube%NetBSD.org@localhost "See the look on my face from staying too long in one place [...] every time the morning breaks I know I'm closer to falling" KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
Attachment:
pgp_L4fVndMLa.pgp
Description: PGP signature