> Whilst I might wish to ultimately replace the OpenAFS userspace utilities with > my own set, that's no small piece of work, and so a handy halfway stage is a > mixed environment as outlined above. > > Furthermore, the ability to use the OpenAFS userspace utilities unmodified > with my kernel module, and, indeed vice-versa, makes testing much easier. But if we add an ABI we end up stuck with it and this one is really really rather ugly. Can you not put pioctl() into a C library linked with the openafs utilities that generates more sensible interface calls ? I mean you have to produce the pioctl() syscall wrapper anyway so why not make "pioctl" a user space compat library ? Alan -- 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
