Re: knfsd rejects everyone on SparcLinux 2.1.89

Erwin J. van Eijk (eijk@huygens.org)
Thu, 09 Apr 1998 09:50:10 +0200


>> Well, as far as I can tell, on Intel this is caused by libc using
>> uint64_t as a dev_t, and the kernel using short as dev_t. I created
>> some fixes in the nfs-0.4.22 stuff, and now it works quite well. Under
>> the provision that the client does not try to establish the
>> whereabouts from a server by sending a null packet to the
>> server. (Ultrix 4.3 does this unfortunately)
cc> Where could I get your patch ? I am extremely interested with that...
cc> (fortunately, we have no Ultrices, only Solaris 2.5.1 clients. In the
cc> interim, I'll happy to let your modifs have a go...)

Ehm, I'll put the building tarball on our ftp site:

ftp://ftp.huygens.org/pub/linux/knfsd/linux-nfs-0.4.22-1.tar.gz

It's 0.4.22 based, and it works over here.

cc> Well, someone told me a few hours after my initial post that on his i386
cc> and Alphas, that was working fine. Maybe a slightly different casting
cc> convention from short to uint64, across architectures.

Possibly, I don't know enough about sparcs to judge....

>> What's your base distribution? Redhat?
cc> Yes. RH4.2 off ftp.lip6.fr (but pretty everything has been recompiled
cc> since, I just kept python1.4 together with python1.5, short of having
cc> found their RPM support module).
cc> (now using the 2.1.91 kernel)

Hmm, I noticed the difference in sizes of dev_t for RedHat 5.0, so
maybe things won't work as well as it ought to, but you can give it a
try. At least things work over here with this version, running kernel
2.1.93, no patches applied.

EJ

--
+--------------------+ There's only one rule:
| Erwin J.  van Eijk | 		The golden rule.
| eijk@acm.org       | He who owns the gold, rules.
+--------------------+

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu