public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@drdos.com>
To: jonathan@jonmasters.org
Cc: Christoph Hellwig <hch@infradead.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>, Robert Love <rml@novell.com>,
	Ankit Jain <ankitjain1580@yahoo.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: processor affinity
Date: Wed, 29 Sep 2004 13:43:32 -0600	[thread overview]
Message-ID: <415B1064.1080302@drdos.com> (raw)
In-Reply-To: <35fb2e5904092913081a802944@mail.gmail.com>

Jon Masters wrote:

>On Wed, 29 Sep 2004 13:24:42 -0600, Jeff V. Merkey <jmerkey@drdos.com> wrote:
>
>  
>
>>Anyway, I
>>provided it as a reference since it is the first patent on SMP affinity
>>scheduling and methods for the very interested person who asked. And
>>yes, Linux
>>appears to infringe it, but since Novell is pro-Linux, I don't think it
>>matters.
>>    
>>
>
>Still it's probably worth knowing it might be an issue someday. What's
>Novell's position on patents they hold involving the kernel? I'm too
>lazy to go hunting for it (rml might well know).
>
>Jon.
>
>  
>
Since they are hiring as many top Linux folks as possible, and they have 
invested their entire future in Linux, I think
their actions speak so loud, it doesn't matter what your hearing from 
them. Novell's position (from my experience)
it that they will take whatever steps they feel necessary to protect 
their circle (as evidenced by an illegal search of
my home by Novell Security Employees (not law enforcement 8 Novell 
employees and a sheriff) ) along with spending
17 million dollars in litigation costs to keep me out of the computer 
business for almost 4 years by crushing me, my
family, and any business I tried to start, and ruining my life and my 
marriage with my previous wife of 24 years).

If you are in their circle, they will fight for you to the death, and 
breaking the rules doesn't bother them.
If you are outside their circle ........ you should feel very safe and 
comfortable.

Linux is in their circle at present. I think you should weigh the 
options and make the appropriate decisions
when choosing to deal with them.

Jeff



  reply	other threads:[~2004-09-29 20:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 12:25 processor affinity Ankit Jain
2004-09-28 13:39 ` Toon van der Pas
2004-09-28 13:47 ` Jon Masters
2004-09-28 13:55 ` Neil Horman
2004-09-28 14:04 ` Jeff V. Merkey
2004-09-28 15:58   ` Robert Love
2004-09-28 16:02     ` Jeff V. Merkey
2004-09-28 21:51       ` Alan Cox
2004-09-29 16:56         ` Jeff V. Merkey
2004-09-29 17:45           ` Christoph Hellwig
2004-09-29 19:24             ` Jeff V. Merkey
2004-09-29 20:08               ` Jon Masters
2004-09-29 19:43                 ` Jeff V. Merkey [this message]
2004-09-29 20:28                   ` Jon Masters
2004-09-29 20:03                     ` Jeff V. Merkey
2004-09-30  2:39           ` Nick Piggin
     [not found]             ` <20040930124708.GA2520@galt.devicelogics.com>
2004-10-01  3:09               ` Nick Piggin

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=415B1064.1080302@drdos.com \
    --to=jmerkey@drdos.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ankitjain1580@yahoo.com \
    --cc=hch@infradead.org \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.com \
    /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