> I've read many messages concerning the "new" libc6 and associated problems. > Why libc6? What does it do for Linux that libc5 does not?
- Better compliance with the standards. Most of the problems we see in moving to libc6, are caused by the non-conforming oddities of libc5. - Libc6 is actually gnu libc 2, wich means that we now (with libc6) use the gnulibc again. So, there's no double efford any more, like there was after linux libc and gnulibc split (OK, I believe not much work was done during most of the time of the split). - Hopefully, all linux systems (not just Debian ones) use the headers from the libc package for /usr/include/linux/..., not from whatever kernel the user has installed. Right from when Debian started doing this, this proved very usefull to us, but other people had to be re-convinced every other week. Maybe when everybody uses our scheme, this re-convincing isn't needed any more. Probably lots more, though. -- joost witteveen, [EMAIL PROTECTED] Potentially offensive files, part 5: /dev/random. `head -c 4 /dev/random` may print 4-letter words (once every approx 4e8 tries). -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .