public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
Cc: Bernd Petrovitsch <bernd@firmix.at>, Petr Baudis <pasky@suse.cz>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Faustian Pact between Novell and Microsoft
Date: Tue, 7 Nov 2006 22:57:49 +0100	[thread overview]
Message-ID: <20061107215748.GA7796@elf.ucw.cz> (raw)
In-Reply-To: <4550E910.6010107@wolfmountaingroup.com>

Hi!

> >>>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.

> <snip>
> 
> /"Microsoft made it clear that only SUSE users and developers, as well 
> as unsalaried Linux developers, are protected. 'Let me be clear about 
> one thing, we don't license our intellectual property to Linux because 
> of the way Linux licensing GPL framework works, that's not really a 
> possibility,' said Microsoft chief executive, Steve Ballmer. 'Novell is 
> actually just a proxy for its customers, and it's only for its 
> customers,' he added. 'This does not apply to any forms of Linux other 
> than Novell's SUSE Linux. And if people want to have peace and 
> interoperability, they'll look at Novell's SUSE Linux. If they make 
> other choices, they have all of the compliance and intellectual property 
> issues that are associated with that.'"
> 
> </snip>
> 
> And those lights are bright indeed ....

Would you care to elaborate? All sorts of red lights are "on" here
from friday, some of them flashing...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2006-11-07 21:58 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 [this message]
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
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=20061107215748.GA7796@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=bernd@firmix.at \
    --cc=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasky@suse.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