linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: whywontyousue@waifu.club
To: Stephan von Krawczynski <skraw.ml@ithnet.com>
Cc: linux-kernel@vger.kernel.org, bruce@perens.com, rms@gnu.org,
	moglen@columbia.edu, blukashev@sempervictus.com,
	tcallawa@redhat.com, editor@lwn.net, skraw.ml@ithnet.com,
	torvalds@osdl.org
Subject: Re: General Discussion about GPLness
Date: Tue, 25 Feb 2020 03:56:44 +0000	[thread overview]
Message-ID: <e02b9131897a194aaec834c9393aab68@waifu.club> (raw)
In-Reply-To: <20200224150124.7c88cb8a@ithnet.com>

I see that you're just going to ignore
Universal City Studios Inc v Reimerdes

Instead you address your emotional issues. This is the making of a 
beast: which is what you are. Driven by your instincts.

You want to violate the linux copyright. You announced your intent 
(which increases the damages you are liable for under US jurisprudence.)

The facts are simple: You may not execute the scheme you are suggesting. 
If you do execute the scheme you or suggesting, or if you assist others 
in doing so then you are liable for copyright infringement (direct or 
contributory). If you make over 1000 dollars off of this infringement 
you are liable for criminal penalties as-well.

The courts see unlicensed modification of another copyright-holders 
work, in memory, while running, as the creation of an unlicensed 
derivative work.

It does not matter how you try to sugar coat it or change your 
description, nor do your complaints of me CC'ing relevant parties (a 
diversion technique by you) who could explain this all to you in ways 
you could understand, change anything. The courts in the USA see this 
type of action you suggest as the creation of a derivative work.

Thus you must follow the permissions and must not overstep them. That is 
all. Having non-gpl modules work as you describe violates the linux 
kernel copyright just as the plugin in the Reimerdes case violated the 
RealPlayer copyright: in both cases the situation involves "modules" 
extending the running program in real-time, in both cases the "modules" 
are not permitted by the copyright owners to do as they wish: and the 
Court agreed.

On 2020-02-24 14:01, Stephan von Krawczynski wrote:
> On Mon, 24 Feb 2020 07:46:33 +0000
> whywontyousue@waifu.club wrote:
> 
>> > Hm, really it is quite hard to stay calm reading your constant insults
>> > on
>> 
>> If such is so, it is shown to all that you are a stupid white man, 
>> what
>> can I say. You can't separate facts from fiction (opinion)
>> [...]
> 
> Please stop spamming people completely unrelated to this thread.
> And please stop spamming this thread with insults and blatant 
> ignorance.
> Thank you.
> No more answers from me to you.
> --
> Regards,
> Stephan

  reply	other threads:[~2020-02-25  3:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 11:03 General Discussion about GPLness whywontyousue
2020-02-23 12:33 ` Stephan von Krawczynski
2020-02-23 12:56   ` whywontyousue
2020-02-23 14:39     ` Stephan von Krawczynski
2020-02-23 16:24       ` whywontyousue
2020-02-23 20:47         ` Stephan von Krawczynski
2020-02-23 23:46           ` Bernd Petrovitsch
2020-02-24 10:29             ` Stephan von Krawczynski
2020-02-25 13:33               ` Bernd Petrovitsch
2020-02-24  7:46           ` whywontyousue
2020-02-24 14:01             ` Stephan von Krawczynski
2020-02-25  3:56               ` whywontyousue [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-23 10:14 Stephan von Krawczynski

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=e02b9131897a194aaec834c9393aab68@waifu.club \
    --to=whywontyousue@waifu.club \
    --cc=blukashev@sempervictus.com \
    --cc=bruce@perens.com \
    --cc=editor@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moglen@columbia.edu \
    --cc=rms@gnu.org \
    --cc=skraw.ml@ithnet.com \
    --cc=tcallawa@redhat.com \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).