some heads up here
glibc-2.7 has sat in ~arch for much longer than i would have liked. the only
real issue holding it back is nscd. i never use this thing myself, but on
some arches (like ppc), it's known to eat your cpu like a dirty C-globbler
(where C is short for CPU). on other arches, it's known to just cream itself
for fun and then promptly exit.
glibc-2.8 is supposed to be out soonish, and if nscd insists on continuing to
be a pile, i'm afraid of having to just dump in a bunch of reverts. nscd in
glibc-2.6.1 seems to be generally OK.
-mike
glibc-2.7 has sat in ~arch for much longer than i would have liked. the only
real issue holding it back is nscd. i never use this thing myself, but on
some arches (like ppc), it's known to eat your cpu like a dirty C-globbler
(where C is short for CPU). on other arches, it's known to just cream itself
for fun and then promptly exit.
glibc-2.8 is supposed to be out soonish, and if nscd insists on continuing to
be a pile, i'm afraid of having to just dump in a bunch of reverts. nscd in
glibc-2.6.1 seems to be generally OK.
-mike