public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Karl <ktatgenhorst@earthlink.net>
Cc: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>, linux-kernel@vger.kernel.org
Subject: Re: Kernel module ethics.
Date: Wed, 27 Feb 2002 18:13:33 -0800	[thread overview]
Message-ID: <20020227181333.A25723@work.bitmover.com> (raw)
In-Reply-To: <20020228005152.GB8858@arthur.ubicom.tudelft.nl> <NDBBJHDEALBBOIDJGBNNCEOFCFAA.ktatgenhorst@earthlink.net>
In-Reply-To: <NDBBJHDEALBBOIDJGBNNCEOFCFAA.ktatgenhorst@earthlink.net>; from ktatgenhorst@earthlink.net on Wed, Feb 27, 2002 at 08:03:31PM -0500

On Wed, Feb 27, 2002 at 08:03:31PM -0500, Karl wrote:
> >>A couple of months ago Larry McVoy gave this excellent advice:
> 
>  >> If you really want to know where you stand, it'll cost you around
>  >> $15K and that, in my opinion, is fine. If it isn't worth $15K to
>  >> protect your code then it is worth so little to you that there really
>  >> is no good reason not to just GPL it from the start.
> 
>     I hope this is not to ignorant a question: From your post I do not
> understand what costs around $15k 

The law is a strange place.  If you really want to know what your rights
are, you need to go pay a lawyer and figure it out.  People think that
words of the GPL is the end of the story.  It's not.  Licenses are only
real after they have been tested in court.  We can all believe that the
GPL is perfect/great/whatever, and it doesn't matter.  A court of law
can look at it and say that it is crap and that's that.  Virtually all
licenses have a clause:

      If  any provision of this License is held to be unenforce-
      able, such provision shall be reformed only to the  extent
      necessary to make it enforceable.

Why is that?  Because the writers know that the license is kaka until
it is tested in court.

The most interesting question about the GPL is where does it stop?
If I link some non-GPLed .o's with GPLed source, is the source for the
.o's GPLed?  Nope, probably not.  Even the GPL acknowledges that it
can't cross certain boundaries, with the "reasonably separable" clause.
In the eyse of the law, if I can substitute in other .o's which do the
same thing as the first set of .o's, then that's a boundary.  Or at
least that's one of the things my $15K taught me.

Like I said before, unless your code is potentially worth at least a
million bucks, it's almost certainly not worth anything financially,
so GPL it.  If you think it could be worth $1M, isn't it worth $.015M
to figure out your rights?
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  parent reply	other threads:[~2002-02-28  2:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 21:11 Kernel module ethics Allo! Allo!
2002-02-27 21:33 ` Cyrille Chepelov
2002-02-27 22:23 ` Richard B. Johnson
2002-02-28  0:51   ` Erik Mouw
2002-02-28  1:03     ` Karl
2002-02-28  2:03       ` Erik Mouw
2002-02-28  2:13       ` Larry McVoy [this message]
2002-02-28  1:38         ` Karl
2002-03-04 14:07         ` Rogier Wolff
2002-02-28  2:37       ` John Jasen
2002-02-28  3:59     ` Richard Thrapp
2002-02-28 17:52       ` Jeff V. Merkey
2002-03-01  0:22       ` Alan Cox
2002-02-28  1:20   ` Rik van Riel
2002-02-27 22:37 ` Greg KH
2002-02-28  9:42 ` Helge Hafting
2002-02-28 13:55   ` Reid Hekman
2002-02-28 16:04   ` Mark H. Wood
2002-02-28 18:31     ` David Lang
  -- strict thread matches above, loose matches on Subject: below --
2002-02-27 21:57 Jesper Juhl
2002-02-28 12:05 Alexander Sandler
2002-03-01  0:53 ` Erik Mouw

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=20020227181333.A25723@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=J.A.K.Mouw@its.tudelft.nl \
    --cc=ktatgenhorst@earthlink.net \
    --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