public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Erwin Rol <erwin@muffin.org>
Cc: linux-kernel@vger.kernel.org, RTAI users <rtai@rtai.org>
Subject: Re: RTAI/RtLinux
Date: Sat, 25 May 2002 09:05:37 -0700	[thread overview]
Message-ID: <20020525090537.G28795@work.bitmover.com> (raw)
In-Reply-To: <1022317532.15111.155.camel@rawpower>

On Sat, May 25, 2002 at 11:05:32AM +0200, Erwin Rol wrote:
> Both Linus and Larry seem to be not very interested in hard-realtime
> Linux additions, this is OK. 

I'm interested in hard realtime.  I'm extremely uninterested in changes 
to the mainline source base in order to get them.  That's exactly why
I like the RT/Linux approach so much, it is the least invasive to the
kernel and - surprise - also has the best performance.

If people were to learn that real time and multi-user throughput are 
by definition mutually exclusive, I'd be a lot happier.  As it is,
we have the SGI/Montevista crowd cramming their stuff into the kernel
and each "little" thing makes the kernel a less pleasant place to be
and brings it one step closer to the point when it gets abandoned 
like ever other OS in the history of our field.

> Also apparently there is the idea that all RTAI developers want to
> become rich by getting the patent out of the way and sell RTAI. 

So the thing I have a problem with is that Victor says that all GPL
is fine.  You say you are all GPL.  So far, no problem.  Yet you keep
coming back and saying there is a problem, that Linux is going to
be out of the running as a real time platform because of the patent.
I don't get it, why should the patent prevent Linux from being used?
All it does is say "if you aren't making money, we aren't making money,
if you are making money, we want a cut".  That seems OK to me, in fact,
it seems more than OK.  It seems like someone who is trying to help
those who are helping others and charge those who are charging others.
That's smart, that's good.  It means that FSMlabs will be here 20 years
from now, still supporting this stuff, whereas all the "we'll survive
off of support" people will have long since gone under.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  parent reply	other threads:[~2002-05-25 16:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-25  9:05 RTAI/RtLinux Erwin Rol
2002-05-25  9:16 ` RTAI/RtLinux Erwin Rol
2002-05-25 13:30 ` RTAI/RtLinux Alan Cox
2002-05-25 13:42   ` RTAI/RtLinux Erwin Rol
2002-05-25 13:21     ` RTAI/RtLinux Der Herr Hofrat
2002-05-25 15:08       ` RTAI/RtLinux Erwin Rol
2002-05-25 16:05 ` Larry McVoy [this message]
2002-05-25 16:28   ` RTAI/RtLinux Karim Yaghmour
2002-05-25 16:30   ` RTAI/RtLinux Erwin Rol
2002-05-25 17:31   ` RTAI/RtLinux Randy.Dunlap
2002-05-25 17:40     ` RTAI/RtLinux Eric Brunner-Williams in Portland Maine
2002-05-25 18:04       ` RTAI/RtLinux Randy.Dunlap
2002-05-25 17:42     ` RTAI/RtLinux Wolfgang Denk
2002-05-26  4:03   ` RTAI/RtLinux Kevin O'Connor
2002-05-26  4:17     ` RTAI/RtLinux Alexander Viro
2002-05-26  4:18     ` RTAI/RtLinux Larry McVoy
     [not found] <57.c083d0f.2a237c49@aol.com>
2002-05-27 12:36 ` RTAI/RtLinux Wolfgang Denk
     [not found] <a0.2767541f.2a239ebb@aol.com>
2002-05-27 15:18 ` RTAI/RtLinux Wolfgang Denk

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=20020525090537.G28795@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=erwin@muffin.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtai@rtai.org \
    /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