From: Arjan van de Ven <arjan@infradead.org>
To: Patrick McFarland <diablod3@gmail.com>
Cc: Anonymous User <anonymouslinuxuser@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: GPL Violation?
Date: Thu, 17 Aug 2006 08:54:16 +0200 [thread overview]
Message-ID: <1155797656.4494.24.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200608170242.40969.diablod3@gmail.com>
On Thu, 2006-08-17 at 02:42 -0400, Patrick McFarland wrote:
> On Thursday 17 August 2006 01:48, Anonymous User wrote:
> > I work for a company that will be developing an embedded Linux based
> > consumer electronic device.
> >
> > I believe that new kernel modules will be written to support I/O
> > peripherals and perhaps other things. I don't know the details right
> > now. What I am trying to do is get an idea of what requirements there
> > are to make the source code available under the GPL.
>
> I am not a lawyer, and I suggest your company speak with one before doing
> this. (And most likely, someone from the list will correct me if I get
> something wrong).
>
> However, your company only has to release any code they use, preferably in the
> form of unmodified tarballs (pointing to project websites for downloads isn't
> valid anymore) plus patches against said unmodified tarballs if modified. If
> not modified, you still have to release the unmodified tarballs.
>
> They don't have to release source code for any module you wrote from scratch
> themselves, but said modules cannot say they are GPL (ie, they have to poison
> the kernel).
Just as a warning: This is your own legal opinion/advice, one which is
apparently not shared with many other kernel developers, including me.
For example see Greg's OLS keynote:
http://www.kroah.com/log/2006/07/23/#ols_2006_keynote
or some of Linus' emails on this topic:
http://cvs.fedora.redhat.com/viewcvs/*checkout*/rpms/kernel/devel/COPYING.modules?rev=1.5
I hope you have talked to a lawyer about your advice, but I sort of
doubt it since your answer doesn't sound like something a lawyer will
tell you (it sure doesn't match what the various lawyers I talked to
told me, not at all)
Anyway the best advice for anyone who asks such a question is to go talk
to a lawyer, and probably he should take a few of those links printed
out with him just to alert the lawyer about the controversial nature of
things.
Greetings,
Arjan van de Ven
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
next prev parent reply other threads:[~2006-08-17 6:54 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 5:48 Anonymous User
2006-08-17 6:14 ` Arjan van de Ven
2006-08-17 9:38 ` Ben B
2006-08-17 12:02 ` linux-os (Dick Johnson)
2006-08-17 16:11 ` Stefan Richter
2006-08-17 19:21 ` James Courtier-Dutton
2006-08-17 23:26 ` Ian Stirling
[not found] ` <20060817193540.dc819396.seanlkml@sympatico.ca>
2006-08-17 23:35 ` Sean
2006-08-18 0:32 ` Alan Cox
2006-08-18 7:23 ` Xavier Bestel
2006-08-18 12:23 ` Ian Stirling
2006-08-18 9:04 ` Helge Hafting
2006-08-17 6:42 ` Patrick McFarland
2006-08-17 6:54 ` Arjan van de Ven [this message]
2006-08-17 7:32 ` Patrick McFarland
2006-08-17 8:02 ` Adrian Bunk
2006-08-17 9:03 ` Patrick McFarland
2006-08-18 17:56 ` Adrian Bunk
2006-08-17 12:39 ` Grzegorz Kulewski
2006-08-17 13:41 ` Alan Cox
2006-08-17 13:31 ` Grzegorz Kulewski
2006-08-17 15:52 ` Theodore Tso
2006-08-18 2:03 ` Chase Venters
2006-08-17 8:32 ` Stefan Richter
2006-08-17 9:36 ` Patrick McFarland
2006-08-17 11:25 ` Alan Cox
2006-08-17 11:48 ` Neil Brown
2006-08-17 9:37 ` David Woodhouse
2006-08-17 23:45 ` Ian Stirling
2006-08-18 8:28 ` David Woodhouse
2006-08-18 12:52 ` Ian Stirling
2006-08-18 8:53 ` Bernd Petrovitsch
2006-08-18 9:04 ` David Woodhouse
2006-08-18 9:15 ` Bernd Petrovitsch
2006-08-20 22:05 ` Andrea Arcangeli
2006-08-20 22:20 ` Arjan van de Ven
2006-08-18 9:51 ` David Schwartz
2006-08-18 16:52 ` Alan Cox
2006-08-18 22:42 ` David Schwartz
2006-08-19 10:48 ` David Greaves
2006-08-19 16:29 ` Patrick McFarland
2006-08-19 17:28 ` David Greaves
2006-08-19 11:30 ` Helge Hafting
2006-08-19 15:44 ` Michael Buesch
2006-08-19 23:01 ` David Schwartz
2006-08-20 3:20 ` Chase Venters
2006-08-21 7:58 ` Helge Hafting
2006-08-21 11:27 ` Stefan Richter
2006-08-21 13:06 ` Alan Cox
2006-08-21 14:59 ` Horst H. von Brand
2006-08-17 9:30 ` Alan Cox
2006-08-17 9:29 ` Patrick McFarland
2006-08-17 14:52 ` Helge Hafting
2006-08-17 14:58 ` Anonymous User
2006-08-17 15:52 ` Stefan Richter
2006-08-17 16:19 ` Michiel de Boer
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=1155797656.4494.24.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=anonymouslinuxuser@gmail.com \
--cc=diablod3@gmail.com \
--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®