public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: "Adam J. Richter" <adam@freya.yggdrasil.com>, alan@lxorguk.ukuu.org.uk
Cc: gilad@benyossef.com, linux-kernel@vger.kernel.org, lm@bitmover.com
Subject: Re: business models [was patent stuff]
Date: Tue, 28 May 2002 19:52:09 +0200	[thread overview]
Message-ID: <E17Cl8k-0004eq-00@starship> (raw)
In-Reply-To: <200205281713.KAA22774@freya.yggdrasil.com>

On Tuesday 28 May 2002 19:13, Adam J. Richter wrote:
> Alan Cox responds to Gilad Ben-Yossef about licensing of Linux-based patents:
> >I don't think you can realistically expect all open source licenses like
> >the BSD one to be accomodated. Otherwise people would ship binary apps
> >linked with a BSD licensed libpatent.o/c that was useless to anyone. The
> >GPL restrictions happen to work very nicely in terms of making a patent
> >available for free software (or one definition thereof), the BSD license
> >alas doesn't.
> 
> 	You could license all programs that consist entirely of
> free software.  That way, BSD, LGPL, and MPL software that did
> not link in proprietary software would be allowed too,

That's a good start, but it's not enough.  There remains the question of
additional restrictions relating to other programs/hardware/whatever.  The 
Fsmlabs RTLinux patent license is a good example of such additional 
restrictions.  This license restricts the royalty-free grant to software 
that is not realtime, or to software that cannot be freely modified.  The
license does not discriminate on the basis of linking, as the GPL does, but
rather, on the nature of the application.

While it's an open question whether or not this is a suitable way for
Fsmlabs to license their patent, it seems clear that similar restrictions
would be entirely inappropriate for a Linux vendor.

-- 
Daniel

  reply	other threads:[~2002-05-28 17:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 17:13 business models [was patent stuff] Adam J. Richter
2002-05-28 17:52 ` Daniel Phillips [this message]
2002-05-28 18:22 ` Alan Cox
2002-05-28 17:23   ` Andre Hedrick
2002-05-29 21:44   ` David Weinehall
2002-05-30  4:51     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2002-05-29 19:13 Adam J. Richter
2002-05-29  3:21 Adam J. Richter
2002-05-29 13:15 ` Alan Cox
2002-05-29 14:13   ` Jonathan Corbet
2002-05-29 16:15     ` Jamie Lokier
2002-05-29 17:29       ` Nicholas Knight
2002-05-31 20:17         ` Perry The Cynic
2002-06-03 10:49   ` Rob Landley
     [not found] <50.c105234.2a24c92d@aol.com>
2002-05-28 13:42 ` Gilad Ben-Yossef
2002-05-27 21:52 patent on O_ATOMICLOOKUP [Re: [PATCH] loopable tmpfs (2.4.17)] Adam J. Richter
2002-05-27 22:24 ` business models [was patent stuff] Larry McVoy
2002-05-27 23:15   ` Karim Yaghmour
2002-05-27 23:31     ` Austin Gonyou
2002-05-28  9:29     ` Peter Wächtler
2002-05-28 13:46       ` Mark Mielke
2002-05-29  8:34         ` Peter Wächtler
2002-05-28  7:53   ` Gilad Ben-Yossef
2002-05-28  8:57     ` Daniel Phillips
2002-05-28 11:30       ` Alan Cox
2002-05-28 10:32   ` Ingo Oeser
2002-05-28 12:28   ` Jonathan Corbet
2002-05-28 18:35   ` Eric W. Biederman

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=E17Cl8k-0004eq-00@starship \
    --to=phillips@bonn-fries.net \
    --cc=adam@freya.yggdrasil.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gilad@benyossef.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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