From: Mike Acar <mike@contract.kent.edu>
To: linux@cthulhu.engr.sgi.com
Subject: Re: M$ 's strategy against Linux: nightmare scenario
Date: Fri, 05 Dec 1997 16:31:02 -0500 [thread overview]
Message-ID: <199712052132.NAA22370@sgi.sgi.com> (raw)
In-Reply-To: Your message of Fri, 5 Dec 1997 10:27:22 -0800 (PST) <199712051827.KAA54904@oz.engr.sgi.com>
[Snip: Linus works for Transmeta, which Microsoft might buy in order to
"acquire" Linux. Legal or not, the legal fight might hamper Linux's spread well
enough to significantly reduce the threat to NT.]
This isn't a particularly big worry to me. The GPL aside, Linus's contract with
Transmeta almost definitely states specifically that Transmeta has no rights at
all to software Linus wrote before he was employed there; similarly, it almost
definitely excludes rights to software Linus writes on his own time. Further,
I'm not sure how much of the kernel Linus actually "owns" anymore; my
understanding (flawed it may be) is that he's primarily coordinating kernel
release and design, and not actually writing nearly as much code as he did. If
this is the case, Linus himself might not be able to claim ownership of the
kernel anymore.
Of course, I'm not a lawyer, so I speak from a position of significant
ignorance; handfuls of salt all round. But I really don't think that MS is going
to be able to use intellectual property to attack Linux.
What does worry me, however, is that Intel, MS and others are making significant
progress in taking control of the PC architecture. With the patented Slot-One
and Slot-Two, Intel is putting serious pressure on its competitors in the
motherboard markets; between Slot-One, Slot-Two, and buying the Alpha, I expect
the threat to Intel's dominance of the PC CPU market to virtually disappear.
The I2O SIG will control access to the hardware docs on the next generation of
fast PCs, and the licensing terms - let alone the SIG member's veto power over
membership applicants - are in fundamental conflict with Linux and the other
free PC Unices. Microsoft might not need to try to crush Linux directly; there's
a distinct possibility that Linux simply won't run on the next generation of
PCs.
But maybe that's just my negativity speaking. I doubt that even a large part of
the PC industry would like to see the architecture grow proprietary; perhaps SGI
could lead the way in providing a design for a new PC-class architecture which
is Open Hardware compliant/approved.
Along those lines, are there any plans for providing Linux drivers for the
Wintel hardware SGI's announced for next summer?
--
Mike Acar - mike@contract.kent.edu - "This autumn is sad beyond belief." - Kafka
next prev parent reply other threads:[~1997-12-05 21:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-05 18:27 M$ 's strategy against Linux: nightmare scenario Ariel Faigon
1997-12-05 18:27 ` Ariel Faigon
1997-12-05 21:31 ` Mike Acar [this message]
1997-12-05 22:20 ` Ariel Faigon
1997-12-05 22:20 ` Ariel Faigon
1997-12-05 22:46 ` Warner Losh
1997-12-05 22:46 ` Warner Losh
1997-12-05 23:08 ` Eric Kimminau
1997-12-06 0:15 ` Chad Campbell
1997-12-07 18:26 ` Eric Kimminau
1997-12-05 23:54 ` William J. Earl
1997-12-05 23:54 ` William J. Earl
1997-12-06 23:16 ` cypher
1997-12-06 23:26 ` cypher
1997-12-06 23:35 ` ralf
1997-12-05 22:43 ` Alan Cox
1997-12-05 22:43 ` Alan Cox
1997-12-06 9:35 ` Michael Neuffer
1997-12-06 23:37 ` cypher
1997-12-06 23:32 ` cypher
1997-12-05 23:44 ` Chad Campbell
1997-12-06 12:42 ` Lige Hensley
1997-12-06 19:06 ` Greg Chesson
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=199712052132.NAA22370@sgi.sgi.com \
--to=mike@contract.kent.edu \
--cc=linux@cthulhu.engr.sgi.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