From: Giacomo Catenazzi <cate@debian.org>
To: Andre Hedrick <andre@linux-ide.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TAINTED (Re: spinlocks, the GPL, and binary-only modules)
Date: Thu, 21 Nov 2002 10:13:00 +0100 [thread overview]
Message-ID: <3DDCA39C.7040602@debian.org> (raw)
In-Reply-To: <fa.ng6tk8v.6nq3q2@ifi.uio.no>
> If Linux is to truly only a GPL binary module friendly environment, then
> it must enforce the rules. Therefore it must forcablely reject the
> attempt to load any and all binaries which are not GPL. Regardless if the
> license is commerial yet the source code is available.
>
Read GPL!
I can modify/create *private* and completly *non-free* code, and link to GPL,
legally. [I cannot distribute it, but kernel should not block me!]
nvidia unfortunatly use this, to not to disclose the complete sources]
And I can use an other OSI approved license, GPL compatible,
but if it is not yet recognized by kernel? Should kernel include all free
licences strings?
ciao
giacomo
next parent reply other threads:[~2002-11-21 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ng6tk8v.6nq3q2@ifi.uio.no>
[not found] ` <fa.ni4rlmv.3gc2ob@ifi.uio.no>
2002-11-21 9:13 ` Giacomo Catenazzi [this message]
2002-11-21 2:25 spinlocks, the GPL, and binary-only modules Rik van Riel
2002-11-21 5:10 ` TAINTED (Re: spinlocks, the GPL, and binary-only modules) Andre Hedrick
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=3DDCA39C.7040602@debian.org \
--to=cate@debian.org \
--cc=andre@linux-ide.org \
--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
all inboxes | Powered by JetHome®