From: "Kevin D. Wooten" <kwooten@home.com>
To: TimO <hairballmt@mcn.net>, Ben Greear <greearb@candelatech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Module Licensing?
Date: Tue, 30 Oct 2001 00:24:52 -0700 [thread overview]
Message-ID: <01103000245200.01138@newton.cevio.com> (raw)
In-Reply-To: <01102920463500.03524@newton.cevio.com> <3BDE27BE.3569FE22@candelatech.com> <3BDE3360.80731876@mcn.net>
In-Reply-To: <3BDE3360.80731876@mcn.net>
On Monday 29 October 2001 21:58, TimO wrote:
> Ben Greear wrote:
> > "Kevin D. Wooten" wrote:
> > > After reading the posts about the MODULE_LICENSE macro, I am in
> > > disbelief. I was under the impression that one could write a
> > > "closed-source" module and distribute it in binary form, and be in
> > > compliance. Please tell me I am wrong? We use Linux as a platform for
> > > some data acquisition, and we are currently distributing ( in very
> > > limited quantity to people who would already have signed an NDA )
> > > modules that currently have no official license as yet. We are
> > > researching which license to use, but according to these post's we have
> > > almost no choice, Open Source or not at all!
> >
> > No, you just can't use certain symbols if you're not GPL. If your
> > code already works, then you're fine, as previously existing symbols
> > will not be thus restricted... You can just make your MODULE_LICENSE ==
> > "mine-all-mine...including-all-my-bugs"
>
> Ugghh! Don't confuse/equate MODULE_LICENSE with EXPORT_SYMBOL_GPL_ONLY;
> two different animals, two differnet goals. See archives for more info.
>
My apologies for the misinterpretation.
This scheme seems fine as long as driver related symbols are not "GPL" only.
> > Ben
> >
> > > -kw
> > > -
next prev parent reply other threads:[~2001-10-30 10:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 3:46 Module Licensing? Kevin D. Wooten
2001-10-30 4:08 ` Ben Greear
2001-10-30 4:58 ` TimO
2001-10-30 5:10 ` Ben Greear
2001-10-30 7:24 ` Kevin D. Wooten [this message]
2001-10-30 17:27 ` Timur Tabi
2001-10-30 23:10 ` Alan Cox
2001-10-31 0:13 ` Timur Tabi
2001-10-31 0:25 ` Alan Cox
2001-10-31 16:53 ` Timur Tabi
2001-10-31 17:10 ` Rik van Riel
2001-10-31 17:22 ` Larry McVoy
2001-10-31 17:27 ` Rik van Riel
2001-10-31 18:34 ` Larry McVoy
2001-10-31 18:44 ` Rik van Riel
2001-10-31 18:53 ` Andreas Dilger
2001-10-31 20:08 ` Craig Milo Rogers
2001-10-31 17:32 ` dean gaudet
2001-10-31 19:55 ` [OT] " Craig Milo Rogers
2001-10-31 21:42 ` Cort Dougan
2001-10-31 23:47 ` Jamie Lokier
2001-10-31 23:54 ` Larry McVoy
2001-11-01 0:10 ` Jamie Lokier
2001-11-01 0:43 ` Alan Cox
2001-11-01 23:52 ` n0ano
2001-10-31 17:29 ` Timur Tabi
2001-10-31 17:37 ` Rik van Riel
2001-10-31 18:31 ` LLX
2001-11-08 0:36 ` drizzt.dourden
2001-11-08 12:41 ` Alan Cox
2001-11-08 13:19 ` Drizzt Do'Urden
2001-11-08 14:53 ` Module Licensing? (thinking a little more) Drizzt Do'Urden
2001-11-08 15:56 ` Doug McNaught
2001-11-08 17:00 ` Drizzt Do'Urden
2001-11-08 17:18 ` Russell King
2001-11-08 17:47 ` Drizzt Do'Urden
2001-11-09 7:50 ` Stefan Smietanowski
2001-11-10 18:09 ` QuoteMstr - Danny Colascione
2001-11-08 17:29 ` Doug McNaught
2001-11-08 19:28 ` drizzt.dourden
2001-10-31 20:15 ` Module Licensing? Craig Milo Rogers
2001-10-31 19:49 ` Craig Milo Rogers
2001-11-04 3:37 ` Albert D. Cahalan
2001-10-31 17:11 ` Alan Cox
2001-11-05 4:40 ` [file interface] " Roger Larsson
2001-10-30 9:22 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01103000245200.01138@newton.cevio.com \
--to=kwooten@home.com \
--cc=greearb@candelatech.com \
--cc=hairballmt@mcn.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).