From: "David S. Miller" <davem@jenolan.rutgers.edu>
To: sca@refugee.engr.sgi.com
Cc: lm@neteng.engr.sgi.com, carlson@heaven.newport.sgi.com,
linux@cthulhu.engr.sgi.com
Subject: Re: Getting X on Linux/SGI
Date: Fri, 20 Jun 1997 04:16:39 -0400 [thread overview]
Message-ID: <199706200816.EAA07911@jenolan.caipgeneral> (raw)
In-Reply-To: <199706200759.AAA02253@refugee.engr.sgi.com> (message from Steve Alexander on Fri, 20 Jun 1997 00:59:06 -0700)
Date: Fri, 20 Jun 1997 00:59:06 -0700
From: Steve Alexander <sca@refugee.engr.sgi.com>
lm@neteng (Larry McVoy) writes:
>We own MIPS. MIPS sold or licensed 19.2 million chips last year. About
>19 million of those were of the type "program the bare metal".
MIPS Chips != SGI systems. My question still stands.
All your assertion proves is that today IRIX is the "enabling"
software technology which puts "SGI systems" out the door.
Don't get me wrong, I was constantly reminded what keeps the lights on
in bldg. 9 when I was there last summer, but when and if Linux begins
to do some (not all) of that "enabling", people might begin to
perceive the situation a bit differently.
next prev parent reply other threads:[~1997-06-20 8:22 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-20 7:59 Getting X on Linux/SGI Steve Alexander
1997-06-20 7:59 ` Steve Alexander
1997-06-20 8:16 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-06-24 0:55 Steve Alexander
1997-06-22 17:50 Larry McVoy
1997-06-22 17:50 ` Larry McVoy
1997-06-23 19:43 ` Christopher W. Carlson
1997-06-22 17:36 Larry McVoy
1997-06-20 21:43 Steve Alexander
1997-06-20 21:43 ` Steve Alexander
1997-06-20 16:45 Larry McVoy
1997-06-20 17:06 ` Todd Shrider
1997-06-20 16:40 Larry McVoy
1997-06-20 16:51 ` Mike Shaver
1997-06-20 16:51 ` Mike Shaver
1997-06-20 16:59 ` richard offer
1997-06-20 8:39 Steve Alexander
1997-06-20 15:22 ` Martin Knoblauch
1997-06-20 7:34 Larry McVoy
1997-06-20 9:55 ` William Fisher
1997-06-20 9:17 ` David S. Miller
1997-06-20 10:12 ` Ralf Baechle
1997-06-20 10:12 ` Ralf Baechle
1997-06-20 20:16 ` Nigel Gamble
1997-06-20 9:55 ` William Fisher
1997-06-20 13:42 ` Todd Shrider
1997-06-20 14:07 ` Ralf Baechle
1997-06-20 14:07 ` Ralf Baechle
1997-06-20 7:21 Steve Alexander
[not found] ` <sca@refugee.engr.sgi.com>
1997-06-20 17:28 ` Christopher W. Carlson
1997-06-23 7:07 ` Martin Knoblauch
1997-06-23 19:31 ` Christopher W. Carlson
1997-06-18 23:16 Larry McVoy
1997-06-18 23:42 ` Nigel Gamble
[not found] ` <nigel@cthulhu.engr.sgi.com>
1997-06-19 15:46 ` Christopher W. Carlson
1997-06-19 6:40 ` Ralf Baechle
1997-06-19 6:40 ` Ralf Baechle
[not found] <199706181641.JAA05598@darwin.esd.sgi.com>
1997-06-18 19:41 ` John Chen
1997-06-18 19:41 ` John Chen
1997-06-18 19:56 ` David S. Miller
1997-06-18 20:15 ` Alex deVries
1997-06-19 20:01 ` William J. Earl
1997-06-18 0:00 Good news: no more begging for HW John Wiederhirn
1997-06-18 0:34 ` Getting X on Linux/SGI Ariel Faigon
1997-06-18 0:34 ` Ariel Faigon
1997-06-18 16:28 ` Christopher W. Carlson
1997-06-18 19:30 ` Nigel Gamble
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=199706200816.EAA07911@jenolan.caipgeneral \
--to=davem@jenolan.rutgers.edu \
--cc=carlson@heaven.newport.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=lm@neteng.engr.sgi.com \
--cc=sca@refugee.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