mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Adam J. Richter" <adam@freya.yggdrasil.com>,
	gilad@benyossef.com, linux-kernel@vger.kernel.org,
	lm@bitmover.com, phillips@bonn-fries.net
Subject: Re: business models [was patent stuff]
Date: Wed, 29 May 2002 23:44:45 +0200	[thread overview]
Message-ID: <20020529234445.O9911@khan.acc.umu.se> (raw)
In-Reply-To: <200205281713.KAA22774@freya.yggdrasil.com> <1022610136.4124.131.camel@irongate.swansea.linux.org.uk>

On Tue, May 28, 2002 at 07:22:16PM +0100, Alan Cox wrote:
> On Tue, 2002-05-28 at 18:13, Adam J. Richter wrote:
> > 	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, but your
> > example of a proprietary program that linked in the BSD'ed
> > libpatent.o/c would not be covered by this permission.
> 
> Define "free software" using only legally defined phrases which have
> precedent. In fact put four people in a room and get them to define free
> software.
> 
> > software would address issues like GPL'ed software that contains
> > content that is GPL compatible but not GPL'ed, future versions of
> 
> If its linked then it is GPL in the linked form, otherwise you wouldn't
> be allowed to link it

An interesting question is whether the licensing terms used for this
patent would pass the DFSG (Debian Free Software Guidelines)?!


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Maintainer of the v2.0 kernel   //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  parent reply	other threads:[~2002-05-29 21:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 17:13 Adam J. Richter
2002-05-28 17:52 ` Daniel Phillips
2002-05-28 18:22 ` Alan Cox
2002-05-28 17:23   ` Andre Hedrick
2002-05-29 21:44   ` David Weinehall [this message]
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=20020529234445.O9911@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --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 \
    --cc=phillips@bonn-fries.net \
    /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

all inboxes | Powered by JetHome®