lkml.org 
[lkml]   [2001]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: MODULE_LICENSE and EXPORT_SYMBOL_GPL
so are you saying that BSD licened modules are not going to be allowed to
use any future entry points (assuming they are all put under the the
export_symbol_gpl limits)?

saying that existing stuff will not change doesn't answer the problem
about licences that may have source avilable (tainting) but may not. if
you assume either way you will cause a bunch of problems.

David Lang

On Thu, 18 Oct 2001, John Alvord wrote:

> Date: Thu, 18 Oct 2001 17:46:18 -0700
> From: John Alvord <jalvo@mbay.net>
> To: David Lang <david.lang@digitalinsight.com>
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: MODULE_LICENSE and EXPORT_SYMBOL_GPL
>
> On Thu, 18 Oct 2001 15:38:36 -0700 (PDT), David Lang
> <david.lang@digitalinsight.com> wrote:
>
> >so what will the export_symbol_gpl stuff do with the BSD license? it may
> >or may not have source avilable so is it allowed to use the exported
> >symbols or not?
> >
> >for the tainting module process there is the same problem.
> >
> >knowing the license the code was released under does not tell you if the
> >source is available or not.
> Linus said that all existing entry points would remain untagged. Thus
> existing modules would not be affected.
>
> john
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:08    [W:0.054 / U:1.924 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site