All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: ralf@uni-koblenz.de
Cc: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com,
	adevries@engsoc.carleton.ca, richard@infopact.nl
Subject: Re: linus.linux.sgi.com
Date: Fri, 15 Jan 1999 19:21:36 -0800	[thread overview]
Message-ID: <199901160321.TAA11493@dm.cobaltmicro.com> (raw)
In-Reply-To: <19990115225918.25643@uni-koblenz.de> (ralf@uni-koblenz.de)

   From: ralf@uni-koblenz.de
   Date: Fri, 15 Jan 1999 22:59:18 +0100

   Seconded.  SGI (and actually the whole industry) is _W_A_Y_ more
   OSS friendly than /. rumors say.

Although I am a supporter of SGI and I understand their friendlyness
to the community, I do have to state that the rumors and feelings are
unsurprising given that:

1) SGI has no UNIX story (yet) on their new hardware.
2) SGI has no binary compatability story on the new hardware for
   customers who have made an investment in their MIPS line.
   (Sun will be acquiring what SGI has (ability to execute x86
    binaries) in the very near future in their Sparc processors,
    without screwing their customers over the way SGI is at the
    moment... I can't say how they'll do it, but all I can say is
    that they are doing it the right way)

And todays announcement of how much of their MIPS investment stake
they are getting rid of, will only amplify how people feel about the
above.

So if SGI has some exciting news for us OSS people in the pipeline,
and they are just holding off for "the right time", I think this is a
miscalculated delay and will hurt them tremendously.  The sooner the
better, is anyone listening?

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

  reply	other threads:[~1999-01-16  3:23 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       ` David S. Miller [this message]
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           ` linus.linux.sgi.com David S. Miller
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=199901160321.TAA11493@dm.cobaltmicro.com \
    --to=davem@dm.cobaltmicro.com \
    --cc=adevries@engsoc.carleton.ca \
    --cc=ariel@cthulhu.engr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.