public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: Pavel Machek <pavel@ucw.cz>, Petr Baudis <pasky@suse.cz>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Faustian Pact between Novell and Microsoft
Date: Tue, 07 Nov 2006 15:12:25 -0700	[thread overview]
Message-ID: <455104C9.4040901@wolfmountaingroup.com> (raw)
In-Reply-To: <1162937650.3408.2.camel@gimli.at.home>

Bernd Petrovitsch wrote:

>On Tue, 2006-11-07 at 09:54 -0700, Jeff V. Merkey wrote:
>  
>
>>Bernd Petrovitsch wrote:
>>
>>    
>>
>>>On Tue, 2006-11-07 at 09:18 +0100, Pavel Machek wrote:
>>>[...]
>>> 
>>>
>>>      
>>>
>>>>This is a watershed moment for Linux. It fundamentally changes the
>>>>rules of the game. We're really excited about this deal, and we hope
>>>>you are too.
>>>>   
>>>>
>>>>(from http://www.novell.com/linux/microsoft/openletter.html) only make
>>>>it worse, but acquisition? I'd hope not even mickey$oft has enough
>>>>cash for _that_.
>>>>        
>>>>
>[...]
>  
>
>>>And the first point in the list is "patents" ....
>>>      
>>>
>[...]
>  
>
>>I can see the lights are coming on now for some folks now. 
>>    
>>
>
>How many patenst does Novell have? Do they play in the "more than 1000
>trivial, prior art and software patents" league like M$?
>So from Novell's point of view it is probably somewhat a cross-licensing
>deal.
>"What does M$ really gain from it?" is the interesting question.
>
>	Bernd
>  
>
The Pike patent from the USL acquisition is the one Microsoft most 
wanted to get their hands on, as well as the SMP
patents.  The Pike patent controls overlapping Windows.     M$ has 
wanted to get clear of it for some time.  With the
cross license from Novell, they are home free.  Novell has a large 
number of networking and directory patents. 

Not quite 1000, but they have some very good ones on SMP, clustering, 
and form the USL acquisition.

Jeff

  reply	other threads:[~2006-11-07 22:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 23:14 Faustian Pact between Novell and Microsoft Jeff V. Merkey
2006-11-02 23:41 ` Jesper Juhl
2006-11-02 23:45   ` Jeff V. Merkey
2006-11-03  1:49 ` Petr Baudis
2006-11-03  3:16   ` Jeffrey V. Merkey
2006-11-03 22:46     ` Bernd Petrovitsch
2006-11-04 22:56       ` Eduard Giménez
2006-11-07  8:18     ` Pavel Machek
2006-11-07 10:17       ` Bernd Petrovitsch
2006-11-07 16:54         ` Jeff V. Merkey
2006-11-07 17:47           ` Gene Heskett
2006-11-07 20:14           ` Jeff V. Merkey
2006-11-07 20:37             ` Gene Heskett
2006-11-07 21:57             ` Pavel Machek
2006-11-08  4:57             ` David Schwartz
2006-11-08  5:11               ` Avuton Olrich
2006-11-08  8:56                 ` Bernd Petrovitsch
2006-11-08  9:53                 ` Kyle Moffett
2006-11-07 22:14           ` Bernd Petrovitsch
2006-11-07 22:12             ` Jeff V. Merkey [this message]
2006-11-03 11:40 ` Andreas Jellinghaus
2006-11-03 14:39   ` Gene Heskett
2006-11-03 16:53     ` Jeffrey V. Merkey
2006-11-04 18:33       ` Gene Heskett
2006-11-08 14:10 ` Jarek Poplawski
2006-11-08 19:45   ` Stephen Hemminger
2006-11-08 22:13     ` Alan Cox

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=455104C9.4040901@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=bernd@firmix.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=pavel@ucw.cz \
    /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