> Now, assuming I do produce such a userspace library - that does not address > the other requirement: that of using a common set of binaries to manipulate > both OpenAFS and kAFS without the need for recompilation. I presume you > advocate making OpenAFS change to suit your requirements? If you have a library providing pioctl() it can speak brain damage to the OpenAFS module and sensible interfaces otherwise. The problem you are attempting to introduce simply doesn't exist. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
