Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: lm@neteng.engr.sgi.com (Larry McVoy)
To: offer@sgi.com (richard offer)
Cc: linux@morgaine.engr.sgi.com
Subject: Re: FYI - free Windows API
Date: Wed, 18 Jun 1997 19:42:18 -0700	[thread overview]
Message-ID: <199706190242.TAA05701@neteng.engr.sgi.com> (raw)

: Even a company the size of DEC couldn't persuade more than a handful of
: companies to port their code to Alpha/NT, and this one-man-and-his-band will
: succeed ?

A couple of counters to that:

	a) he's giving it away under the GPL.  Linux used that approach
	   and has at least 3 million, some say 6 million, seats.  Linus 
	   didn't get all those seats - he was helped.   This guy is 
	   asking for help.  Maybe we, SGI, and the other Unix vendors
	   should contribute a few percent of our engineering staff to
	   all working on this to catch up with u$oft.  Together we stand,
	   divided we fall - cliche but uite apropos at the moment.

	b) did you miss the part about the 8086 interpreter so that you
	   can just run binaries unmodified?  I haven't tried it but I
	   imagine it works.

As a friend at DEC said - "we need to grow the pie, not shrink it.  Linux
grows it.  We all benefit".  I agree.

WARNING: multiple messages have this Message-ID (diff)
From: lm@neteng.engr.sgi.com (Larry McVoy)
To: richard offer <offer@sgi.com>
Cc: linux@morgaine.engr.sgi.com
Subject: Re: FYI - free Windows API
Date: Wed, 18 Jun 1997 19:42:18 -0700	[thread overview]
Message-ID: <199706190242.TAA05701@neteng.engr.sgi.com> (raw)
Message-ID: <19970619024218.cPpsDSZKMW6v5fixqwabu-EaPnj2xhOW7TbRyGaYld0@z> (raw)

: Even a company the size of DEC couldn't persuade more than a handful of
: companies to port their code to Alpha/NT, and this one-man-and-his-band will
: succeed ?

A couple of counters to that:

	a) he's giving it away under the GPL.  Linux used that approach
	   and has at least 3 million, some say 6 million, seats.  Linus 
	   didn't get all those seats - he was helped.   This guy is 
	   asking for help.  Maybe we, SGI, and the other Unix vendors
	   should contribute a few percent of our engineering staff to
	   all working on this to catch up with u$oft.  Together we stand,
	   divided we fall - cliche but uite apropos at the moment.

	b) did you miss the part about the 8086 interpreter so that you
	   can just run binaries unmodified?  I haven't tried it but I
	   imagine it works.

As a friend at DEC said - "we need to grow the pie, not shrink it.  Linux
grows it.  We all benefit".  I agree.

             reply	other threads:[~1997-06-19  2:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-06-19  2:42 Larry McVoy [this message]
1997-06-19  2:42 ` FYI - free Windows API Larry McVoy
1997-06-19 15:43 ` Martin Knoblauch
  -- strict thread matches above, loose matches on Subject: below --
1997-06-19  2:07 Larry McVoy
1997-06-19  2:07 ` Larry McVoy
     [not found] ` <lm@neteng>
1997-06-19  2:29   ` richard offer
1997-06-19  3:08     ` David S. Miller

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=199706190242.TAA05701@neteng.engr.sgi.com \
    --to=lm@neteng.engr.sgi.com \
    --cc=linux@morgaine.engr.sgi.com \
    --cc=offer@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