From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Nasty Requirements for non-GPL Linux Kernel Modules?
Date: 13 May 2001 11:32:00 +0200 [thread overview]
Message-ID: <80l$fSP1w-B@khms.westfalen.de> (raw)
In-Reply-To: <E14xZNJ-00033f-00@the-village.bc.nu>
In-Reply-To: <20010509114816.K14127@work.bitmover.com> <E14xZNJ-00033f-00@the-village.bc.nu>
alan@lxorguk.ukuu.org.uk (Alan Cox) wrote on 09.05.01 in <E14xZNJ-00033f-00@the-village.bc.nu>:
> > you stand, it'll cost you around $15K and that, in my opinion, is fine.
> > If it isn't worth $15K to protect your code then it is worth so little to
> > you that there really is no good reason not to just GPL it from the start.
>
> Smart advice.
Problem is, the people making that decision are not always the people
wanting to distribute the work in question, in which case the argument
doesn't work.
I don't know more about this specific case than what was said in the
thread, but it sounds like a case in point.
MfG Kai
next prev parent reply other threads:[~2001-05-13 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 17:50 Nasty Requirements for non-GPL Linux Kernel Modules? Scott C. Karlin
2001-05-09 18:06 ` Alan Cox
2001-05-09 18:48 ` Larry McVoy
2001-05-09 18:58 ` mirabilos
2001-05-09 19:11 ` Alan Cox
2001-05-13 9:32 ` Kai Henningsen [this message]
2001-05-13 10:59 ` Mike Galbraith
2001-05-13 18:18 ` Kai Henningsen
2001-05-14 6:21 ` Mike Galbraith
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='80l$fSP1w-B@khms.westfalen.de' \
--to=kaih@khms.westfalen.de \
--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