From: Jan Niehusmann <jan@gondor.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Tim Bird <tbird@lineo.com>, linux-kernel@vger.kernel.org
Subject: Re: Input on the Non-GPL Modules - legal nonsense
Date: Mon, 22 Oct 2001 19:04:24 +0200 [thread overview]
Message-ID: <20011022190424.A25819@gondor.com> (raw)
In-Reply-To: <E15v4Dz-0002VM-00@the-village.bc.nu> <3BD1F5CC.20BF3F20@candelatech.com> <3BD438ED.360D0007@lineo.com> <3BD43BA5.B9E8E557@candelatech.com>
In-Reply-To: <3BD43BA5.B9E8E557@candelatech.com>
On Mon, Oct 22, 2001 at 08:30:45AM -0700, Ben Greear wrote:
> I'm not advocating this as a good thing to do, but I am curious: Can someone
> else take action against this? I hope the answer is yes. This
> whole thing begins to look like MS's attempts at securing digital music:
> there are just too many ways around it. Either way,
Yes, but with a significant difference:
If somebody breaks MS's stuff, MS will probably try to sue him, but the
person gets more popular.
If somebody breaks GPL, there may be nobody to sue him, but it can easily
make him a persona non grata in all kinds of free software and open
source groups. Or, equivalently, if some corporation breaks GPL, this
may cause some very bad PR.
Jan
next prev parent reply other threads:[~2001-10-22 17:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 15:29 Input on the Non-GPL Modules Greg Boyce
2001-10-18 16:00 ` M. R. Brown
2001-10-18 16:32 ` Jan Niehusmann
2001-10-18 17:08 ` Tony Hoyle
2001-10-18 17:15 ` Jan Niehusmann
2001-10-18 19:01 ` Tim Bird
2001-10-18 19:38 ` Rik van Riel
2001-10-20 22:04 ` Alan Cox
2001-10-20 22:08 ` Ben Greear
2001-10-22 15:19 ` Input on the Non-GPL Modules - legal nonsense Tim Bird
2001-10-22 15:30 ` Ben Greear
2001-10-22 17:04 ` Jan Niehusmann [this message]
2001-10-25 6:24 ` David Schwartz
2001-10-26 3:58 ` Rob Landley
2001-10-20 22:20 ` Input on the Non-GPL Modules Anton Altaparmakov
2001-10-21 14:28 ` Alan Cox
2001-10-20 22:58 ` Craig Milo Rogers
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=20011022190424.A25819@gondor.com \
--to=jan@gondor.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tbird@lineo.com \
/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