From: riel@surriel.com (Rik van Riel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel contributions from organisations and individual privacy
Date: Sat, 13 Jun 2015 12:23:49 -0400 [thread overview]
Message-ID: <557C5915.7020909@surriel.com> (raw)
In-Reply-To: <4E5779AD88B2F040B8A7E83ECF544D1A603600@SJCPEX01CL03.citrite.net>
On 06/12/2015 07:29 PM, Jeff Haran wrote:
> What is the downside to a large company for violating GPL? They are likely to not get sued in the first place. If they are they can delay using court procedures until they've changed their code to not violate or GPL'ed it. Worst for them is paying legal fees and a contribution. I am guessing those aren't huge, not for a big company. Seems like unless there is some monetary sting like a piece of the proceeds on the sale of violating products, there is no deterrence and you guys will be in court for the rest of time chasing a never ending stream of new violators.
Creating a new kernel for one's product is not as easy as it sounds.
Even replacing the kernel with a BSD kernel, and then replacing the
userland code, and possibly writing a bunch of new device drivers,
is very much non-trivial.
Replacing Linux with something else in a product could easily cost
several millions of dollars.
--
All rights reversed.
next prev parent reply other threads:[~2015-06-13 16:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 9:19 Kernel contributions from organisations and individual privacy Chris Packham
2015-06-11 4:58 ` Jason Ball
2015-06-11 5:10 ` Chris Packham
2015-06-11 5:19 ` Ruben Safir
2015-06-11 14:28 ` Greg KH
2015-06-11 14:41 ` Ruben Safir
2015-06-11 15:38 ` Greg KH
2015-06-11 16:39 ` Ruben Safir
2015-06-11 17:54 ` Greg KH
2015-06-11 17:57 ` Greg KH
2015-06-11 23:26 ` Ruben Safir
2015-06-11 23:37 ` Rik van Riel
2015-06-11 23:55 ` Ruben Safir
2015-06-12 0:13 ` Jeff Haran
2015-06-12 1:28 ` Rik van Riel
2015-06-12 23:29 ` Jeff Haran
2015-06-13 15:40 ` Bjørn Mork
2015-06-13 19:08 ` Ruben Safir
2015-06-15 23:08 ` Jeff Haran
2015-06-15 23:55 ` Rik van Riel
2015-06-16 16:23 ` Jeff Haran
2015-06-13 16:23 ` Rik van Riel [this message]
2015-06-14 21:18 ` Valdis.Kletnieks at vt.edu
[not found] ` <B424B28F-AB7E-4972-95BB-FF91D85D0FED@gmail.com>
2015-06-14 23:29 ` Valdis.Kletnieks at vt.edu
[not found] ` <557E0FF7.1000607@gmail.com>
2015-06-15 2:08 ` Valdis.Kletnieks at vt.edu
2015-06-12 0:52 ` Greg KH
2015-06-12 3:31 ` Valdis.Kletnieks at vt.edu
2015-06-12 4:39 ` Ruben Safir
2015-06-12 7:18 ` Valdis.Kletnieks at vt.edu
2015-06-11 13:13 ` Rik van Riel
2015-06-11 14:27 ` Greg KH
2015-06-11 14:25 ` Greg KH
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=557C5915.7020909@surriel.com \
--to=riel@surriel.com \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.