From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sidney Cammeresi Subject: Licensing conflict with OpenAFS kernel module Date: Wed, 26 Apr 2006 09:07:07 -0500 Message-ID: <20060426140707.GA6094@cheesecake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I recently upgraded two Xen domU instances from 2.6.12.6 to 2.6.16. Because I am running the OpenAFS client on each of them, I took the opportunity to upgrade that (from 1.4.0 to 1.4.1) which required building a new kernel module. (The AFS client is partly in userspace and partly in the kernel.) Loading the new module failed: openafs: Unknown symbol force_evtchn_callback openafs: Unknown symbol xen_features Upon inspecting the kernel source, I observed that these functions are EXPORT_SYMBOL_GPL. Unfortunately, OpenAFS is licensed under the IBM Public License, which means that the OpenAFS client will no longer run on Xen. This is mostly just an FYI. I solved my problem by editing the source and changing OpenAFS's MODULE_LICENSE to GPL, but obviously OpenAFS cannot distribute that change, so OpenAFS on Xen remains broken for now. Hopefully I won't get any letters from DMCA enforcement lawyers telling me I'm running software illegally.... -- Sidney CAMMERESI http://www.cheesecake.org/sac/