linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Henning P. Schmiedehausen" <mailgate@hometree.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Novell Attacks Linux
Date: Tue, 28 Aug 2001 08:21:28 +0000 (UTC)	[thread overview]
Message-ID: <9mfka8$sb$1@forge.intermeta.de> (raw)
In-Reply-To: <20010825020114.A12724@vger.timpanogas.org> <3B8809A5.DB7B6764@baywinds.org> <20010825153009.B14524@vger.timpanogas.org> <9mcurg$cuo$1@forge.intermeta.de> <20010827122838.A20599@vger.timpanogas.org>

"Jeff V. Merkey" <jmerkey@vger.timpanogas.org> writes:

>People have downloaded NWFS from LKML.  If Novell is making claims
>it's stolen, in the US I have an obligation to inform these people.
>You live in Germany, so I don't expect you to understand our laws.
>Under our law, Novell can go after any of these people, so they 
>need to be warned.

According to my law understanding, people downloaded source code from
a public ftp server on the Internet according to a distribution and
licensing agreement ("GPL") that was issued by the "vendor" (distributor)
called TRG.

If you released code that was "stolen" to the public under a license
that you could not (or were not allowed to) issue, they will go after
you. Not after your customers.

In Germany, there is something called "nach bestem Wissen und
Gewissen" (roughly translated "in best intention"). This would apply
here (under german law of course).

Novell can (in best) demand that everyone who downloaded that code
"cease and desist" to use it. They can hold _you_ as the distributor
responsible for the damage to their business. And that's the reason
why you make politics here. You want to turn "Novell attacks TRG" into
"Novell attacks Linux" because you hope of a possible "fallout" on
Novell. That's what I call "make politics on LKM".

But I know, you're in the country where people marry with 14, may
drive cars with 16, carry guns with 19 but have to wait for being 21
to drink alcohol. 

	Regards
		Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen       -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH     hps@intermeta.de

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   info@intermeta.de
D-91054 Buckenhof     Fax.: 09131 / 50654-20   

  reply	other threads:[~2001-08-28  8:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-25  9:01 Novell Attacks Linux Jeff V. Merkey
2001-08-25 20:25 ` Bruce Ferrell
2001-08-25 22:30   ` Jeff V. Merkey
2001-08-27  8:02     ` Henning P. Schmiedehausen
2001-08-27 19:28       ` Jeff V. Merkey
2001-08-28  8:21         ` Henning P. Schmiedehausen [this message]
2001-08-28 13:49           ` Paul Fulghum
2001-08-29 22:46             ` Jim Roland
2001-08-28 20:30           ` Paul G. Allen
2001-08-30  4:03           ` Jeff V. Merkey
2001-08-30  3:26             ` Erik Andersen
2001-08-30  8:27               ` Jeff V. Merkey
2001-08-30  4:39             ` Trever L. Adams
2001-08-30  5:12               ` Mike Galbraith
2001-08-30  8:30               ` Jeff V. Merkey
2001-08-29 22:05         ` Jim Roland
2001-08-30  3:56           ` Jeff V. Merkey
2001-08-30  0:49 Petr Vandrovec
2001-08-30  4:19 ` Jeff V. Merkey

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='9mfka8$sb$1@forge.intermeta.de' \
    --to=mailgate@hometree.net \
    --cc=hps@intermeta.de \
    --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;
as well as URLs for NNTP newsgroup(s).