On 4/05, Ben Collins wrote: | Was this the glibc 2.1.1-2? If so, it should have been fixed, I tested | it myself on a sun4m/2.2.5(non-cvs) and Steven tested on a | sun4m/2.2.1(stock debian image). If that's the case we need to do some | quick fixing. Yup: glibc (2.1.1-2) unstable; urgency=low I got a big screwup. Could it be due to the fact that I'm running a stock 2.2.6 kernel?