mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dana Lacoste <dana.lacoste@peregrine.com>
To: Mark Mielke <mark@mark.mielke.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A reply on the RTLinux discussion.
Date: 29 May 2002 09:54:06 -0400	[thread overview]
Message-ID: <1022680446.9043.5.camel@dlacoste.ottawa.loran.com> (raw)
In-Reply-To: <20020528213457.A22540@mark.mielke.cc>

On Tue, 2002-05-28 at 21:34, Mark Mielke wrote:
> It is really simple. Either A) Victor has a patent, and code in RTAI
> may need to be licensed, or B) Victor has a patent, and code in RTAI
> does not need to be licensed.

I think this is the main, critical, horrendous point.

RTAI is free, open source software.
whether it is covered by the licence or not, it's allowed by the
free clauses in rtlinux.

The problem here (and i can see why Karim is upset) is that people
who use RTAI to make commercial, closed source software may ALSO be
required to licence RTLinux even though they're using RTAI, not
RTLinux.

This would be retarded.  I mean, seriously, making the linux kernel
require anybody who's doing any commercial real-time stuff pay Victor
because it's in the kernel source and it's patented is just plain dumb.
Linus doesn't want to force anyone to use bitkeeper, why should he force
anyone to pay Victor as well?

Of course I must point out that it's easy for me to speak up : although
I do almost entirely embedded work I have absolutely no use for RT
software here, so I'm not affected at all.  I just see it as a slippery
slope towards BSD :)

Dana Lacoste
Ottawa, Canada


  parent reply	other threads:[~2002-05-29 13:54 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57.c083d0f.2a237c49@aol.com>
2002-05-27 12:36 ` RTAI/RtLinux Wolfgang Denk
2002-05-28 12:04   ` A reply on the RTLinux discussion yodaiken
2002-05-28 14:37     ` Roman Zippel
2002-05-28 15:57       ` Alan Cox
2002-05-28 15:11         ` Roman Zippel
2002-05-28 16:45           ` Alan Cox
2002-05-29  0:31             ` Roman Zippel
2002-05-29  1:34               ` Mark Mielke
2002-05-29  3:11                 ` Karim Yaghmour
2002-05-29  8:53                   ` Zwane Mwaikambo
2002-05-29 13:54                 ` Dana Lacoste [this message]
2002-05-29 15:17                   ` Alan Cox
2002-05-29 14:20                     ` Dana Lacoste
2002-05-29 15:15                       ` Mark Mielke
2002-05-29 17:43                         ` Dana Lacoste
2002-05-29 18:26                           ` Mark Mielke
2002-05-29 15:31                       ` Alan Cox
2002-05-29 15:45                       ` yodaiken
2002-05-29 17:40                         ` Dana Lacoste
2002-06-03 10:09                       ` Rob Landley
2002-05-29 13:24               ` Alan Cox
2002-05-29 13:43                 ` Roman Zippel
2002-05-29 14:59                   ` Alan Cox
2002-05-29 20:18                     ` Roman Zippel
2002-05-31 11:57                 ` Pavel Machek
2002-05-31 21:34                   ` Mark Mielke
2002-05-31 23:19                   ` yodaiken
2002-05-28 15:19     ` Karim Yaghmour
2002-05-28 15:39       ` Mark Mielke
2002-05-28 16:00         ` Karim Yaghmour
2002-06-01 20:37       ` Michael Barabanov
2002-05-28 16:12 James Bottomley
2002-05-28 17:31 ` Roman Zippel
2002-05-28 18:03   ` James Bottomley
2002-05-28 21:21     ` Jeff V. Merkey
2002-05-29  8:58       ` Peter Wächtler
2002-05-29 12:36 Rose, Billy
2002-05-29 19:46 ` Daniel Phillips
2002-05-29 19:58   ` Mark Mielke

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=1022680446.9043.5.camel@dlacoste.ottawa.loran.com \
    --to=dana.lacoste@peregrine.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®