From: Sven Vermeulen <sven.vermeulen@rug.ac.be>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Subject: Re: GPL issuefor run time kernel function overwrite
Date: Mon, 30 Jul 2001 17:26:28 +0200 [thread overview]
Message-ID: <20010730172628.A1078@Zenith.starcenter> (raw)
In-Reply-To: <F56FOSPUPeKljq65Rn800008a48@hotmail.com> <Pine.LNX.3.95.1010730104556.1947A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1010730104556.1947A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Mon, Jul 30, 2001 at 10:48:58AM -0400
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On Mon, Jul 30, 2001 at 10:48:58AM -0400, Richard B. Johnson wrote:
[snip]
> We already have so-called "proprietary" code being included into
> the kernel. This started with "harmless" bits of binary which is
> uploaded into the hardware when some drivers are installed.
> Including such binary is also contrary to GPL, but without this
> secret goo, the hardware won't run.
>
> This exception to GPL, in my opinion, opened the door to future
> corruption and exploitation. Time will tell.
Doesn't the copyright-holder of the work have the final decision wether or
not a non-GPL-modification may be inserted? I think the only change that
should be done then is a notice that this and that is non-GPL but permitted
by the copyright-holder...
Ofcourse, If you aren't the copyright-holder of the work (in his totality),
you need to contact the copyright-holder in order to receive (written)
permission...
Just a thought.
--
Sven Vermeulen - Key-ID CDBA2FDB
LUG: http://www.lugwv.be - http://www.keyserver.net
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-07-30 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 14:14 kumar M
2001-07-29 21:35 ` Alan Cox
2001-07-30 14:48 ` Richard B. Johnson
2001-07-30 15:26 ` Sven Vermeulen [this message]
2001-07-31 0:31 ` Rob Landley
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=20010730172628.A1078@Zenith.starcenter \
--to=sven.vermeulen@rug.ac.be \
--cc=root@chaos.analogic.com \
/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®