mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: business models [was patent stuff]
Date: 28 May 2002 12:35:51 -0600	[thread overview]
Message-ID: <m1n0ukxgqg.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200205272152.OAA03070@adam.yggdrasil.com> <20020527152452.A24502@work.bitmover.com>

Larry McVoy <lm@bitmover.com> writes:

> Jumping on the chance to cause more discussion...  This probably ought to
> be off on some other list, but I don't know what that is.  Alan will be 
> sending out the guards to herd me back into the ward, but I've escaped
> for the moment and I'll make the best of it :)
[snip]
> If you hold the "It's GPL or bugger off" position, people will figure out
> how to work around it and it is virtually certain you won't like what they
> do.  If you offer them some sort of reasonable compromise, I'll bet they
> take it.  If you don't, you get to live with whatever their nasty evil
> business minds dream up.

To a certain extent other people's business model is none of your
business.  The only people who have a reasonable right to ask that
question is the company itself, and it's investors.  And support is
far from being the only viable GPL compatible business model. 

Most new businesses fail, even when they are using known proven
business models.  It is execution, and being in the right place at the
right time that make a successful company. 

For the GPL or bugger off folks, unless you have a business model
that delivers GPL'd code to them, you don't make any money from them.
Not offering them the GPL violates ``The customer is always right''.
Of course it is perfectly fine to concentrate on those people who you
can figure out how to make money from.

There is only one test for a successful business model, is the company
here making money 20 years from now.  That test is going to take a
while.

Eric

  parent reply	other threads:[~2002-05-28 18:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2002-05-27 23:26 ` patent on O_ATOMICLOOKUP [Re: [PATCH] loopable tmpfs (2.4.17)] Alan Cox
     [not found] <50.c105234.2a24c92d@aol.com>
2002-05-28 13:42 ` business models [was patent stuff] Gilad Ben-Yossef
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
2002-05-30  4:51     ` Greg KH
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
2002-05-29 19:13 Adam J. Richter

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=m1n0ukxgqg.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.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

all inboxes | Powered by JetHome®