Harald Barth wrote:
Welcome to the madhouse where unknown conventions lure under the floor boards ;-)My project entails implementing some of the OpenAFS functionality into the RedHat kAFS code. This will allow for people wanting to use OpenAFS to have code directly in the Linux kernel, as compared to needing to patch the kernel, and then needing the correct version of OpenAFS, etc.Take the arla kernel module, call it kAFS and most of your tasks are allready done. Yes, the code is dual licensed.
As far as I am aware Arla is not shipped as part of the Linux kernel and although it does not have the same licensing issues as OpenAFS it is
broken by kernel revisions just as frequently as the OpenAFS module is. Red Hat's kAFS is in the kernel and is not broken each time the Linux kernel developers make changes. At the present time it is not as usable as is necessary but David Howell's has made a lot of progress on the internals. The purpose of this project is to ensure that the interfaces for pioctls or xattrs used for configuration, the keyring design for PAGs, etc. are common between kAFS and OpenAFS. That way when kAFS functionality is at the level that acceptable for most users that all of the user land tools can be shared by both implementations. Users that wish to have the OpenAFS kmod instead of kAFS can swap the modules and continue on with their lives. There are several other functional features like adding AFSDB support to kAFS that are also a part of the project scope. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
