Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: eak@detroit.sgi.com
Cc: ralf@uni-koblenz.de, ariel@cthulhu.engr.sgi.com,
	linux@cthulhu.engr.sgi.com, adevries@engsoc.carleton.ca,
	richard@infopact.nl
Subject: Re: linus.linux.sgi.com
Date: Mon, 18 Jan 1999 21:19:05 -0800	[thread overview]
Message-ID: <199901190519.VAA17644@dm.cobaltmicro.com> (raw)
In-Reply-To: <36A40CBE.F55CA9F1@detroit.sgi.com> (message from Eric Kimminau on Mon, 18 Jan 1999 23:40:30 -0500)

   Date: Mon, 18 Jan 1999 23:40:30 -0500
   From: Eric Kimminau <eak@detroit.sgi.com>

   As for "screwing their customers", ask Sun when they are going to
   support NT on any of their systems.

Never, whats so wrong with that?  To quote their VP of desktops "One
more Linux user is one less NT user."  I think this makes their stance
on NT pretty obvious.  Also look at their position in the M$ trial.
They have things like WABI, which runs on Sparc right now, so if you
just need the M$ applications, you can run them.

   At least SGI is making it possible to start thinking about doing
   UNIX environment kinds of tasks in the NT world rather than
   snubbing their nose at the people who have made the business
   decision to migrate to that environment.

If everyone jumps off a bridge, should we follow right after them?

I think the problem is the direction of the thinking here.  Why do we
need to bring Unix to NT, if all users want is both environments and
the applications, then bring NT to Unix since we know Unix is better
(sic) and has fewer fallacies than NT does.

   As for "no UNIX story" on the 320 or 540 hardware, all I can say is
   that there have been a lot of Linux rumors. Nothing substantiated.

And here is the point I was trying to make, rumors aren't going to get
anywhere.  SGI is taking too long to commit if they do have something
in the pipeline, everything is up in the air, and the best this does
is either:

1) Give the rumors (right or wrong) more weight than an official
   statement, until such a statement is made.
2) Put question marks above the heads of everyone else.

   HP uses Intel CPU's. Compaq now owns DEC. Who says SGI has to own
   the company that makes the CPU's we put in our systems? 

I never said that.  All I said was that it would have been wiser to
give users a one SGI platform family migration scheme, ie. have a
family of MIPS machine that ran what the next generation machine would
(even if only at such a level to assure successful ports)...  It's
like the difference between:

1) A bomb is about to drop, assume the position.

and

2) A bomb is dropping in a month, here are the tools and resources to
   build a shelter for yourselves so you are prepared.

   For being an SGI supporter, this sure sounds like Sun FUD, IMHO.

I am a supporter, but this does not mean I need to close my eyes when
I believe very bad decisions are being made.  That would make me a
sheep.  I think SGI's stalling is a mistake, so I'm going to talk
about it.

When I was an intern at SGI, I told people things like this.  I'm very
outspoken, and I'll tell people when they make mistakes, and I'll also
make suggestions about future decisions when I am listened to about
such matters.

The "everyone else's shit stinks except mine" mentality has been the
source of failure behind a few engineering teams and companies out
there.  I think SGI is doing some cool stuff, the hardware looks
impressive.  I also think Sun is doing a lot of nice stuff too.  I
choose to learn from what both of them are doing, instead of being a
blind pundit for one or the other.

Later,
David S. Miller
davem@dm.cobaltmicro.com

  reply	other threads:[~1999-01-19  5:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-15 18:24 linus.linux.sgi.com Alex deVries
1999-01-15 18:28 ` linus.linux.sgi.com Eric Kimminau
1999-01-15 18:44 ` linus.linux.sgi.com Richard Hartensveld
1999-01-15 19:09   ` linus.linux.sgi.com Ariel Faigon
1999-01-15 19:09     ` linus.linux.sgi.com Ariel Faigon
1999-01-15 21:29     ` linus.linux.sgi.com Alan Cox
1999-01-15 21:59     ` linus.linux.sgi.com ralf
1999-01-16  3:21       ` linus.linux.sgi.com David S. Miller
1999-01-18 10:40         ` linus.linux.sgi.com Ariel Faigon
1999-01-18 10:40           ` linus.linux.sgi.com Ariel Faigon
1999-01-18 17:25           ` linus.linux.sgi.com Miguel de Icaza
1999-01-18 17:25             ` linus.linux.sgi.com Miguel de Icaza
1999-01-19  4:40         ` linus.linux.sgi.com Eric Kimminau
1999-01-19  5:19           ` David S. Miller [this message]
1999-01-19 11:21             ` linus.linux.sgi.com dmanddmer
1999-01-19 15:30               ` linus.linux.sgi.com David Watters
1999-01-19 16:46               ` linus.linux.sgi.com Alex deVries
1999-01-19 15:05             ` linus.linux.sgi.com David Watters
1999-01-15 22:38     ` linus.linux.sgi.com Miguel de Icaza
1999-01-15 22:06 ` linus.linux.sgi.com William J. Earl
  -- strict thread matches above, loose matches on Subject: below --
1999-01-28 22:07 linus.linux.sgi.com Ulf Carlsson
1999-01-23  2:07 linus.linux.sgi.com ralf
1998-06-14 20:35 linus.linux.sgi.com Alex deVries
1998-06-15 18:02 ` linus.linux.sgi.com Bob Mende Pie
1998-06-15 18:11   ` linus.linux.sgi.com Alex deVries

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=199901190519.VAA17644@dm.cobaltmicro.com \
    --to=davem@dm.cobaltmicro.com \
    --cc=adevries@engsoc.carleton.ca \
    --cc=ariel@cthulhu.engr.sgi.com \
    --cc=eak@detroit.sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    --cc=richard@infopact.nl \
    /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