Just for record:

Problem here is that Linux glibc mistakely interprets some information
it's not supposed to interpret. It's entirely Linux glibc brokeness.

Unfortunately, we can't fix Linux glibc. We need to deal with this broken
behaviour in our kernel compat/linux code, and massage the provided
values so that Linux glibc would not bomb.

This problem is completely orthogonal to NetBSD libc, which doesn't
make any assumptions similar to the ones made by Linux glibc.

Jaromir

rick@snowhite.cis.uoguelph.ca wrote:
> Hi,
> 
> > I actually implemented that back when I redid the cookie stuff. The 
> > '-X' option to mount_nfs will do this, it uses the already available
> > cookie hash table to generate a fake 32 bit value. It's documented
> > in the compat_linux.8 manpage, even.
> 
> That sounds fine to me. (I'll be wantin' to get that code merged in with the
> 4.4 stuff someday. No rush though, it'll be quite a while before V4 is ready
> to hit the streets.) I was assuming that the references to glibc were talking
> about stuff already linked into a Linux binary, so it couldn't be fixed. But,
> if it's a shared library that can be fixed, that sounds better, to me. As you
> can tell, I'm completely out of date w.r.t. what NetBSD has in it:-)
> 
> Best of luck with it, rick
> 


-- 
Jaromir Dolecek <jdolecek@NetBSD.org> http://www.NetBSD.org/Ports/i386/ps2.html
-=- We should be mindful of the potential goal, but as the tantric    -=-
-=- Buddhist masters say, ``You may notice during meditation that you -=-
-=- sometimes levitate or glow.   Do not let this distract you.''     -=-