From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Anonymous User <anonymouslinuxuser@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL Violation?
Date: Thu, 17 Aug 2006 10:30:37 +0100 [thread overview]
Message-ID: <1155807037.15195.50.camel@localhost.localdomain> (raw)
In-Reply-To: <40d80630608162248y498cb970r97a14c582fd663e1@mail.gmail.com>
Ar Mer, 2006-08-16 am 22:48 -0700, ysgrifennodd Anonymous User:
> I suspect the company will try to get away with releasing as little as
> possible. I don't know much about the GPL or Linux kernel internals,
> but I want to encourage the company I work for to give back to the
> community.
You should read the GPL license (its fairly plain English). Any matters
of doubt should be discussed with someone qualified to discuss then
(such as a lawyer).
In terms of general policy
- The GPL requires you make source available to your customers by one of
several means (mail in, zip archive on the CD with the manual etc). It
is considered "polite" to also make the changes available publically on
the web somewhere as well.
- There are bodies such as the CE Linux Forum that may be useful to you
and the company.
> I understand that modifications to GPL code must be released under the
> GPL. So if they tweak a scheduler implementation, this must be
> released. What if a new driver is written to support a custom piece
> of hardware? Yes, the driver was written to work with the Linux
> kernel, but it isn't based off any existing piece of code.
Basically if it is a derivative work (see your lawyer). This is a
non-trivial area of law so really you should ask your lawyer not a bunch
of programmers.
Alan
--
"Some people are like Slinkies...
Not really good for anything,
but they still bring a smile to your face
when you push them down a flight of stairs."
-- Gordon Wolfe.
next prev parent reply other threads:[~2006-08-17 9:09 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
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 [this message]
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=1155807037.15195.50.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=anonymouslinuxuser@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®