All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Tim Bird <tbird@lineo.com>
Cc: no To-header on input 
	<"unlisted-recipients:;;"@www.candelatech.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Input on the Non-GPL Modules - legal nonsense
Date: Mon, 22 Oct 2001 08:30:45 -0700	[thread overview]
Message-ID: <3BD43BA5.B9E8E557@candelatech.com> (raw)
In-Reply-To: <E15v4Dz-0002VM-00@the-village.bc.nu> <3BD1F5CC.20BF3F20@candelatech.com> <3BD438ED.360D0007@lineo.com>

Tim Bird wrote:
> 
> 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...")

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,
I've had my say on this topic...and will let it RIP.

Ben

> 
> 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
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

  reply	other threads:[~2001-10-22 15:30 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 [this message]
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=3BD43BA5.B9E8E557@candelatech.com \
    --to=greearb@candelatech.com \
    --cc="unlisted-recipients:;;"@www.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.