From: "Jeff V. Merkey" <jmerkey@utah-nac.org>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: gene.heskett@verizon.net, linux-kernel@vger.kernel.org
Subject: Re: [Fwd: United States Patent: 6,862,609]
Date: Thu, 03 Mar 2005 08:48:00 -0700 [thread overview]
Message-ID: <422731B0.6040007@utah-nac.org> (raw)
In-Reply-To: <1109845583.28561.19.camel@tara.firmix.at>
Bernd Petrovitsch wrote:
>On Wed, 2005-03-02 at 21:28 -0700, Jeff V. Merkey wrote:
>
>
>>Gene Heskett wrote:
>>
>>
>>>On Wednesday 02 March 2005 21:36, Jeff V. Merkey wrote:
>>>
>>>
>>>>Another Linux patent.....
>>>>
>>>>
>
>... and another - AFAICS obvious - trivial ("prior art") patent (but I'm
>not fluent in patent quak, I'm just a simple systems engineer).
>
>And one more reason to sent the European software patent directive
>simply to hell, clarify in §52.2 to not patentability of "software"
>discarding the word play of the patent attorneys and offices and get
>into the head of the folks of the EPO (with whatever means are
>necessary).
>
>
>
>>>And that pretty much says it. Assigned to the Canopy Group. So SCO
>>>will have yet another lawsuit to threaten us with. If they survive
>>>
>>>
>
>Apparently Canopy Group/SCO/... are not of the front of innovation since
>"what is new on a RAID system in any way in 2005"?
>
>
>
>>>the thrashing I've Been Moved will give them at the end of the day.
>>>
>>>
>>>
>>The way to fight the patents is for Linux developers to file their own
>>and start putting down stakes.
>>
>>
>
>Or simply drop the whole patent system as such. Apparently it is only
>abused to make money of the inventions of others and for sure does not
>help innovation as such in any way (it may help the lawyers, offices and
>companies in that area - patent utilisation - to get rich but that area
>has nothing to do with innovation).
>
> Bernd
>
>
Patent law in the US is based on section 113 of the United States
Constitution, and patents
are not going away. Live with guys. The best way to win the patent
wars is for people
who do Linux development to file their own patents and put some stakes
in the ground.
You guys keep saying, "stop the patents" but this is insanity. It's
like all these big companies
used patents like swords and are hemming linux in, and Linux stands
naked and defenseless.
You guys need to get your own swords and fight -- start filing patents
-- go to this new law
center "Southern Poverty Law Center" they setup I read about and get
these folks to start
filing patents on Linux code (before you disclose it that is) and
protect yourselves. Then
you have ammo to negotiate cross patent agreements with MS and these
other companies
to create a balance of power.
Jeff
next prev parent reply other threads:[~2005-03-03 15:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 2:36 [Fwd: United States Patent: 6,862,609] Jeff V. Merkey
2005-03-03 3:27 ` Gene Heskett
2005-03-03 4:28 ` Jeff V. Merkey
2005-03-03 6:21 ` Gene Heskett
2005-03-03 10:03 ` Måns Rullgård
2005-03-03 10:31 ` Bernd Petrovitsch
2005-03-03 11:22 ` Adrian Bunk
2005-03-03 15:42 ` Jeff V. Merkey
2005-03-04 19:46 ` Tom Vier
2005-03-03 10:26 ` Bernd Petrovitsch
2005-03-03 15:48 ` Jeff V. Merkey [this message]
2005-03-03 16:03 ` Randy.Dunlap
2005-03-03 16:49 ` jmerkey
2005-03-03 17:39 ` James Simmons
2005-03-03 17:55 ` jmerkey
2005-03-03 20:11 ` Trever L. Adams
2005-03-03 20:31 ` Jeff V. Merkey
2005-03-04 11:05 ` Bernd Petrovitsch
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=422731B0.6040007@utah-nac.org \
--to=jmerkey@utah-nac.org \
--cc=bernd@firmix.at \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.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