On Thu, 2006-11-23 at 01:54 -0800, ramana wrote: > First thanks to Ian for providing valuable info for arrving at this > conclusion. > > What happened? There is old autofs4 module which supported autofs4 > protocol. Autofs team developed new autofs5 protocol but new module > given name as autofs4. > > So this is where the problem is. New module is backward compatible with > autofs4 protcol and also supports autofs5 but with the name 'autofs4'. > > Everything ok but with the autofs headers. > > What can be done? > > Until this is resolved, just compile autodir with old > /usr/src/linux/auto_fs4.h and everthing should work fine. > > That is the reason older autodir compiled with older header file > working fine with new kernel module autofs4 (which is autofs5) > > Since I do not have access to new autofs module on my Fedora, the > testing is going fine -- which is compiled with older autofs module. > > And I can not say 100% sure about. (as I said I do not have access to > the latest module and I can not confirm it myself doing tests).
I agree it is unfortunate that the module is named autofs4 not autofs and I apologize for the confusion I have caused. In my view of the world autofs4 should replace autofs in the kernel but that hasn't happened yet and I'm not pushing for it but in time I will. The way it is designed is that the module supports several different protocol versions that need not be related to the name of the module. The version 5 protocol has obviously been added recently and has new message type numbers and they use different size packets. It appears to me that the issue has come up because of the interpretation of the macro AUTOFS_MAX_PROTO_VERSION which is the maximum supported protocol version and is not meant to be used by an application when specifying the version that it wishes to use. The application should actually check the kernel module for the versions it supports at startup using the provided ioctls. I have code to do this (although it needs a little work). At least that's the way it is supposed to work. Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
