public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Roman Zippel <zippel@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: A reply on the RTLinux discussion.
Date: Tue, 28 May 2002 14:21:47 -0700	[thread overview]
Message-ID: <20020528142147.A7353@vger.timpanogas.org> (raw)
In-Reply-To: <zippel@linux-m68k.org> <200205281803.g4SI3vx05013@localhost.localdomain>



I've been reading all this discussion, and I think the solution
is pretty simple.  Patents are fairly easy to invalidate if you
can show prior art.  Novell and these big software companies 
do it all the time.  When they implement something that infringes
someone's patent, they wait until litigation is filed, then seek to
invalidate specific claims in the patent.  There are administrative
procedures in place wih the USPTO that take this into account.  It's
expensive and you have to be willing to risk litigation.

Patents describe "methods".  If you alter the methods, however slightly,
it makes it tougher for the patent holder to win an infringement case.
Based upon the whirlwind of discussion on this topic, it would seem 
that there is significant deviation from the patent claims to 
circumvent the probability that such claims would succeed.  

The bottom line is you can get sued anyway.  Patent cases are pretty
tough to defend, but the only test will be to implement it, then 
wait for the patent holder to bring claims in US District Court and 
attack the basic claims in the patent on the basis of prior art.  

This RTLinux patent appears, at least on the surface, to be another
software "trash patent".  Microsoft has thousands of such patents,
and it's questionable they will ever be able to win enforcement on 
many of them.  Ditto this case.

Jeff



  reply	other threads:[~2002-05-28 20:54 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 16:12 A reply on the RTLinux discussion James Bottomley
2002-05-28 17:31 ` Roman Zippel
2002-05-28 18:03   ` James Bottomley
2002-05-28 21:21     ` Jeff V. Merkey [this message]
2002-05-29  8:58       ` Peter Wächtler
  -- strict thread matches above, loose matches on Subject: below --
2002-05-29 12:36 Rose, Billy
2002-05-29 19:46 ` Daniel Phillips
2002-05-29 19:58   ` Mark Mielke
     [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
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

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=20020528142147.A7353@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --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