Sergio Gelato <[EMAIL PROTECTED]> wrote: > * Christopher D. Clausen [2005-08-09 19:09:55 -0500]: >> Even more testing has revealed that the libafs64.nonfs.o module works >> just fine when the libafs64.o one does not. This is very weird. I >> can only assume that this is due to some change in Solaris 10. >> >> Am I going to run into weird NFS / AFS problems later on because I am >> using the nonfs kernel module? Can someone explain why there were >> two seperate modules (nonfs and nfs) to begin with? > > If you don't know why there are two separate modules, then the .nonfs. > one is probably right for you. (It's the one I've always used on > Solaris.) > > If I remember correctly, the other one is meant to be used on NFS/AFS > translator machines. The translator functionality may very well be > broken at the moment; I don't use it myself, so I wouldn't know.
from: http://www.openafs.org/pages/doc/QuickStartUnix/auqbg005.htm#HDRWQ46 I was simply going by the single line the IBM docs: "If the machine is running the 64-bit version of Solaris 7, its kernel supports NFS server functionality, and the nfsd process is running:" Since nfsd is indeed running, I thought the "libafs64.o" file was the one I needed. Apparently this is not the case. <<CDC _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
