From: "Dean McEwan" <dean_mcewan@linuxmail.org>
To: jamie@shareable.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Using GPL'd Linux drivers with non-GPL, binary-only kernel
Date: Tue, 13 May 2003 09:08:32 +0000 [thread overview]
Message-ID: <20030513090832.9158.qmail@linuxmail.org> (raw)
>Jamie Lokier wrote :
>>
>> What's the position of kernel developers towards using the GPL'd Linux
>> kernel modules - that is, device drivers, network stack, filesystems
>> etc. - with a binary-only, closed source kernel that is written
>> independently of Linux?
First much kudos goes to Jamies V. modem work which sped up my V.34 devel
quite a lot.
companies who use complex kernel functions are supposed to GPL, it doesn't mean they
do, and lets not tread down that path,lest Andre see me, proprietary modules suck
everybody knows it, they just keep quiet,
dare it desturb them making money.
Linus says in the credits file his position, although such a position is supposed to be taken
from the majority of users and not a few kernel hackers.
Anyway, as im selling a no license version of my software for £13,000 I can hardly complain.
The best opinion on their legality comes from RMS, and although im not a zealot, he did
write the license, Trawl MARC for lawyers, GNU, and RMS and see if you can find it.
Thanks for your help by working on V.
Cheers, Deano.
--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr
Powered by Outblaze
next reply other threads:[~2003-05-13 8:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 9:08 Dean McEwan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 1:23 Using GPL'd Linux drivers with non-GPL, binary-only kernel Jean Tourrilhes
[not found] <BKEGKPICNAKILKJKMHCAAEBCCLAA.Riley@Williams.Name>
2003-05-07 16:57 ` Eric W. Biederman
[not found] <20030506165014$3d57@gated-at.bofh.it>
[not found] ` <20030506193019$0d29@gated-at.bofh.it>
[not found] ` <20030506220018$5b96@gated-at.bofh.it>
2003-05-07 1:17 ` Tony 'Nicoya' Mantler
2003-05-06 16:42 Jamie Lokier
2003-05-06 17:35 ` Alan Cox
2003-05-06 18:54 ` Jamie Lokier
2003-05-06 19:28 ` Jean-Marc Lienher
2003-05-06 19:53 ` Alan Cox
2003-05-06 22:31 ` Jamie Lokier
2003-05-06 21:38 ` Alan Cox
2003-05-08 21:36 ` Pavel Machek
2003-05-06 19:17 ` Eric W. Biederman
2003-05-06 21:55 ` Jamie Lokier
2003-05-06 22:21 ` David Schwartz
2003-05-07 8:21 ` Eric W. Biederman
2003-05-07 14:25 ` Valdis.Kletnieks
2003-05-07 14:31 ` Jamie Lokier
2003-05-07 15:50 ` Eric W. Biederman
2003-05-06 20:43 ` Pavel Machek
2003-05-06 22:18 ` Jamie Lokier
2003-05-06 21:31 ` Alan Cox
2003-05-06 22:48 ` Jamie Lokier
2003-05-07 12:20 ` Alan Cox
2003-05-07 14:26 ` Jamie Lokier
2003-05-07 15:18 ` Pavel Machek
2003-05-08 11:11 ` Krzysztof Halasa
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=20030513090832.9158.qmail@linuxmail.org \
--to=dean_mcewan@linuxmail.org \
--cc=jamie@shareable.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