mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Mielke <mark@mark.mielke.cc>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	yodaiken@fsmlabs.com, linux-kernel@vger.kernel.org
Subject: Re: A reply on the RTLinux discussion.
Date: Tue, 28 May 2002 21:34:57 -0400	[thread overview]
Message-ID: <20020528213457.A22540@mark.mielke.cc> (raw)
In-Reply-To: <Pine.LNX.4.21.0205281702540.17583-100000@serv> <1022604318.4123.114.camel@irongate.swansea.linux.org.uk> <3CF42179.29A2CAED@linux-m68k.org>

On Wed, May 29, 2002 at 02:31:53AM +0200, Roman Zippel wrote:
> Alan Cox wrote:
> > Perhaps you should spend your
> > time thinking instead of insinuating everyone on the planet who isnt
> > working for rtai is a liar ?
> I am watching this whole mess already quite some time and I am trying
> very hard to make sense out of this. Victor pretends to be the nice guy
> here, but if one looks closer, one can see how little respect he has for

I can't speak for Victor, but...

Is it illegal for Victor to keep his options open?

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.

The text for the patent is available. Technical people and lawyers
huddle over a table, decide whether it is worth the risk, and go from
there. This is the way that every company must go under our current
legal structure.

Even if you *did* get a 'straight' answer out of Victor, his words
would not change his ability to sue RTAI. If RTAI needs a license,
they should *get* a license. If they don't need a license, they don't
need a license.

What is clear, is that the wrong question is being asked to the wrong
person. You don't ask Victor whether you can be exempt from potential
risk. You ask Victor for a license (i.e. written down and signed by
his company), or you take the risk, and assume that you do not need a
license. In neither case do you ask "I think my code might infringe on
your patent, can you make a (verbal) statement publicly that you will
look away if indeed you ever, at any time in the future, decide that
it is?"

In fact, if such a question was posed (which I think we have
observed), I would assume that the company posing the question was not
legally responsible, and *I*, as a prospective client in need of a RT
OS for my application, would avoid. The last thing I need is the
company working on my RT OS to be sued and disappear. I would much
prefer to work with the company that has the patent.

But then again - this is the crux of the matter. RTAI is suffering due
to 'patent issues', and RTLinux is not. RTLinux owns the patent, after
all. This couldn't possibly be RTAI whining because they cannot get
a large enough customer base, could it?

Sure there are all sorts of precidences that this sets. However, I have
yet to see any sort of true evolution or development *not* set
precidences.

The only real argument I have seen from RTAI folk is that Victor isn't
being a proper Open Source priest. This may annoy other Open Source
priests, but it does not affect my own opinion of the man. I find the
'Open Source' religion to have no future. I see applications of an
Open Source-style license, but as a religion? As an ability to judge a
person based on some sort of Open Source-defined morality? Nope... no
future.

mark

-- 
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
.  .  _  ._  . .   .__    .  . ._. .__ .   . . .__  | Neighbourhood Coder
|\/| |_| |_| |/    |_     |\/|  |  |_  |   |/  |_   | 
|  | | | | \ | \   |__ .  |  | .|. |__ |__ | \ |__  | Ottawa, Ontario, Canada

  One ring to rule them all, one ring to find them, one ring to bring them all
                       and in the darkness bind them...

                           http://mark.mielke.cc/


  reply	other threads:[~2002-05-29  1:41 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 [this message]
2002-05-29  3:11                 ` Karim Yaghmour
2002-05-29  8:53                   ` Zwane Mwaikambo
2002-05-29 13:54                 ` Dana Lacoste
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=20020528213457.A22540@mark.mielke.cc \
    --to=mark@mark.mielke.cc \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yodaiken@fsmlabs.com \
    --cc=zippel@linux-m68k.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

all inboxes | Powered by JetHome®