[OpenAFS-devel] kabi-tracking kmods

[Troy Benjegerdes]

kABI will work great under the following conditions:

1) large RHEL customer demands OpenAFS support
2) RHEL defines which kabi functions are 'stable'
3) OpenAFS *Foundation* sponsors a mulitple-support vendor project to
   implement the openafs.ko module using *only* kabi supported functions

**OR**

1) someone makes the linux-kernel kafs module work with kinit/aklog.
workshop.openafs.org/afsbpw09/talks/thu_2/kafs.pdf

And then you won't ever have to think about kabi again, because there's
a first-class supported GPL verison of the AFS client.

Oh wait, is IBM going to sue Red Hat for trademark violations of the
'afs' trademark?

On Tue, Sep 25, 2012 at 04:09:52PM -0600, Ken Dreyer wrote:
> Re-reading through the kabi thread[1] from last month, I'm trying to
> understand: Is kABI tracking a lost cause with OpenAFS? Is it just
> better to rebuild for every kernel update?
> 
> My small experience with kabi kmod packages is limited to ATI's video
> drivers and OpenAFS. It has worked sometimes, but other times I've had
> to rebuild against RHEL 6's newer kernels in order to get a module to
> work properly. I'm wondering what's the best direction overall.
> 
> - Ken
> 
> [1] https://lists.openafs.org/pipermail/openafs-devel/2012-August/018944.html
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel