From: Taral <taral@taral.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MODULE_LICENSE and EXPORT_SYMBOL_GPL
Date: Sun, 21 Oct 2001 15:16:50 -0500 [thread overview]
Message-ID: <20011021151650.C13718@taral.net> (raw)
In-Reply-To: <20011019103041.D30774@taral.net> <E15vKR6-0006g5-00@the-village.bc.nu>
In-Reply-To: <E15vKR6-0006g5-00@the-village.bc.nu>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On Sun, Oct 21, 2001 at 04:22:47PM +0100, Alan Cox wrote:
> You are arguably obtaining services by deception, and possibly also
> violating a content management system.
>
> However the MODULE_LICENSE isn't aimed at people like that. In fact I've had
> totally positive responses from people who ship well known binary modules
> and understand why we want them to get bugs related to their code.
>
> The people bright enough to hack insmod generally are also bright enough to
> realise why its a bad idea.
I'm not arguing against MODULE_LICENSE. I'm arguing against
EXPORT_SYMBOL_GPL. I fully agree with the person who mentioned that
calling certain interfaces "restricted" and basing that restriction on
the licence of the interface user is an abuse of copyright.
More reasonable would be to have header files that looked like this:
#ifndef GPL_COMPATIBLE_LICENSE
#error This header file is restricted to GPL-compatible code only.
#endif
--
Taral <taral@taral.net>
This message is digitally signed. Please PGP encrypt mail to me.
"Any technology, no matter how primitive, is magic to those who don't
understand it." -- Florence Ambrose
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2001-10-21 20:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 16:05 MODULE_LICENSE and EXPORT_SYMBOL_GPL Roy Murphy
2001-10-18 15:17 ` Arjan van de Ven
2001-10-19 15:30 ` Taral
2001-10-21 15:22 ` Alan Cox
2001-10-21 20:16 ` Taral [this message]
2001-10-19 17:06 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-10-19 18:03 Roy Murphy
2001-10-18 16:43 Roy Murphy
2001-10-18 15:49 ` Arjan van de Ven
2001-10-18 18:42 ` Tim Bird
2001-10-19 15:38 ` Taral
2001-10-18 16:07 ` Jan-Benedict Glaw
2001-10-18 22:38 ` David Lang
2001-10-19 0:46 ` John Alvord
2001-10-18 23:57 ` David Lang
2001-10-19 12:44 ` Reid Hekman
2001-10-19 20:07 ` David Lang
2001-10-20 0:00 ` Reid Hekman
2001-10-20 6:38 ` Keith Owens
2001-10-21 15:06 ` Alan Cox
2001-10-21 15:47 ` Alan Cox
2001-10-18 3:23 Keith Owens
2001-10-18 4:03 ` Alexander Viro
2001-10-19 7:16 ` Kai Henningsen
2001-10-19 8:26 ` Nils Philippsen
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=20011021151650.C13718@taral.net \
--to=taral@taral.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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