> can't we have both? There's certainly no problem shipping both - what I was thinking about more is which do we link everything against?
i know of at least one bug in glibc that wasn't a candidate for being fixed (last i heard.) it's nfs_readdir() depends on an opaque cookie being a particular style (ie, what linux does) that is not true of virtually any other NFS server. this manifests itself on netbsd under linux emulation for processes doing readdir() on large directories... perhaps initially netbsd libc - it seems to me to be much more likely to work 100% (or close to) with the kernel. after a lot of testing you might want glibc for default (but i'd always hope otherwise :) .mrg. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
