From: David Schwartz <davids@webmaster.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Input on the Non-GPL Modules - legal nonsense
Date: Wed, 24 Oct 2001 23:24:15 -0700 [thread overview]
Message-ID: <20011025062415.AAA15814@shell.webmaster.com@whenever> (raw)
In-Reply-To: <3BD438ED.360D0007@lineo.com>
>I keep hearing this type of reasoning. It flat-out doesn't work this way in
>the legal system. This is similar to arguing that you didn't really stab
>someone if you threw the knife instead of holding it. ("But your honor, once
>the knife left my hand it really wasn't under my control...")
What amazes me is that these legal arguments about the control programmers
have over their software, are coming from the free software community. If
Microsoft argued that anybody who wanted to write a program to link with
Windows system DLLs had to give them 2% of the profits, they'd be blasted by
the press, yet the free software community wants to argue that programmers
can't use their APIs if they don't have certain licensing terms?!
The irony is killing me.
DS
next prev parent reply other threads:[~2001-10-25 6:24 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
2001-10-25 6:24 ` David Schwartz [this message]
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=20011025062415.AAA15814@shell.webmaster.com@whenever \
--to=davids@webmaster.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