From: Tim Bird <tbird@lineo.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: Input on the Non-GPL Modules - legal nonsense
Date: Mon, 22 Oct 2001 09:19:09 -0600 [thread overview]
Message-ID: <3BD438ED.360D0007@lineo.com> (raw)
In-Reply-To: <E15v4Dz-0002VM-00@the-village.bc.nu> <3BD1F5CC.20BF3F20@candelatech.com>
Ben Greear wrote:
>
> Alan Cox wrote:
> >
> > > What prevents the author of a non-GPL module who needs access to a
> > > GPL-only symbol from writing a small GPLed module which imports the
> > > GPL-only symbol (this is allowed, because the small module is GPL),
> > > and exports a basically identical symbol without the GPL-only
> > > restriction?
> >
> > The fact that it ends up GPL'd to be linked (legal derivative work sense)
> > to the GPL'd code so you can link it to either but not both at the same time
>
> If you own the copyright to the small shim GPL piece, can anyone else
> take legal action on your part? If not, then all you have to do is not
> sue yourself for the double linkage and no one else can sue you either....
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...")
If your actions bring about the result, whether
directly or indirectly, you are legally liable for the
consequences.
____________________________________________________________
Tim Bird Lineo, Inc.
Senior VP, Research 390 South 400 West
tbird@lineo.com Lindon, UT 84042
next prev parent reply other threads:[~2001-10-22 15:16 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 ` Tim Bird [this message]
2001-10-22 15:30 ` Input on the Non-GPL Modules - legal nonsense Ben Greear
2001-10-22 17:04 ` Jan Niehusmann
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=3BD438ED.360D0007@lineo.com \
--to=tbird@lineo.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