fr den 15.04.2005 Klokka 12:57 (+0100) skreiv David Howells: > We've come across an interesting problem with NFS4 mount on a PPC64 box. If > the mount program is compiled as PPC32, then the mount() syscall is returned > EFAULT.
So, why is this not a case of "Doctor it hurts..."? In exactly which case do people have absolutely no alternative but to run a 32-bit version of the mount program on top of a kernel that was compiled as PPC64? A simple script that runs "uname -r" and switches a soft-link between the 32-bit and 64-bit version of "mount" is not rocket science. > I would prefer option (4), otherwise we have to find _all_ usages of the > mount() system calls and fix them. mount() is not a documented syscall. The binary formats for filesystems like NFS are only documented inside the kernels to which they apply. There should therefore be exactly ONE instance of usage, and that is in the "mount" program itself. Cheers, Trond -- Trond Myklebust <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
