public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Austin Gonyou <austin@digitalroadkill.net>
To: Karim Yaghmour <karim@opersys.com>
Cc: Larry McVoy <lm@bitmover.com>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	linux-kernel@vger.kernel.org
Subject: Re: business models [was patent stuff]
Date: 27 May 2002 18:31:02 -0500	[thread overview]
Message-ID: <1022542262.29146.19.camel@UberGeek> (raw)
In-Reply-To: <3CF2BE26.4FF03387@opersys.com>

Man..it's like Farenheit 451, but more like "Hex 0xffff"

On Mon, 2002-05-27 at 18:15, Karim Yaghmour wrote:
...
> I predict the inverse. Of course, people will actually try to use patents to
> restrict free and open source software. And of course, they will push this
> as hard and as far as they can. The community, however, will always find
> alternative ways to obtain the same results and, in the end, no client wil
> use the patent holder's products or services. Instead, they will use the
> community's alternative solutions.
> 
> You would like the open source and free software communities to get used
> to having their rights being violated. I think the software "manufacturers"
> better get used to the fact that they can't outsmart the community,
> regardless of the legal/political/financial tools they use.


I tend to agree with Karim here for sure. It's human nature to overcome
adversity, and this is adversity in one frame of mind, not from
different points of view. (Just to clarify the MPAA see adversity in
certain aspects of the OSS community I think, but they're the opressors,
not us).

Also, in the paragraph about "GPL or bugger off", if you feel it's over
the top, then it's possible others will too, and then it's simply
survival of the fittest. People must change to a degree, but the message
they carry is, and probably will remain, the same. 

Austin

  reply	other threads:[~2002-05-27 23:31 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
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=1022542262.29146.19.camel@UberGeek \
    --to=austin@digitalroadkill.net \
    --cc=adam@yggdrasil.com \
    --cc=karim@opersys.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