public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Mark Mielke <mark@mark.mielke.cc>
Cc: Karim Yaghmour <karim@opersys.com>, Larry McVoy <lm@bitmover.com>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	linux-kernel@vger.kernel.org
Subject: Re: business models [was patent stuff]
Date: Wed, 29 May 2002 10:34:06 +0200	[thread overview]
Message-ID: <3CF4927E.7070508@loewe-komp.de> (raw)
In-Reply-To: <200205272152.OAA03070@adam.yggdrasil.com> <20020527152452.A24502@work.bitmover.com> <3CF2BE26.4FF03387@opersys.com> <3CF34DF4.9050905@loewe-komp.de> <20020528094604.A16952@mark.mielke.cc>

Mark Mielke wrote:
> On Tue, May 28, 2002 at 11:29:24AM +0200, Peter Wächtler wrote:
> 
>>Karim Yaghmour wrote:
>>
>>>I agree that this should go on some other list, but 'til then, here
>>>are my 2c.  No offense Larry, but many of your arguments are the
>>>same used by Microsoft to push their vision of publicly available
>>>source.
>>>
>>Just a quick suggestion: keep Linux open (THE operating system) as basis
>>for future development, enhancement. I think it's called "public facility"
>>like power plants and infrastructure that is needed for a healthy society
>>(at least politicians shall work for the publics benefit).
>>
> 
> Just for a quick interjection... under the model you describe, the
> governments of this world should be paying for linux kernel
> development. :-)
> 

Do you vote against that? I'm not.

It does not have to be financed by the government - but it can.
And I think that already happens in smaller amounts in Germany.
The BSI (my translation: ministry for security in information technology)
already sponsors the project SPHINX for developing encrypted email
services (based on GNU gpg). This is only one example.

Why not? Computers are getting more and more important in our daily life.

It's obvious to protect common goods. Microsoft can still develop
their non disclosed products for "more security".
I thought moms and dads would still teach their children:
"If a stranger talks to you, offering chocolate and says: trust me -
run away and ask other for help"

Oh, is that too old fashioned?  ;-)





  reply	other threads:[~2002-05-29  8:33 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 [this message]
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=3CF4927E.7070508@loewe-komp.de \
    --to=pwaechtler@loewe-komp.de \
    --cc=adam@yggdrasil.com \
    --cc=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=mark@mark.mielke.cc \
    /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