From: Warner Losh <imp@bsdimp.com>
To: heinz@osta.com
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] PC Unix (had been How to Kill a Technical Conference
Date: Tue, 6 Apr 2021 19:37:14 -0600 [thread overview]
Message-ID: <CANCZdfqHg4MzgDVMmFg-xyZyJrLtHZ2b4aBGBn2vnFmm+rjy=g@mail.gmail.com> (raw)
In-Reply-To: <aa48d18983c5eb1849f2f912fd3eb213@osta.com>
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
On Tue, Apr 6, 2021 at 7:31 PM <heinz@osta.com> wrote:
> I developed LSX at Bell Labs in Murray Hill NJ in the 1974-1975
> timeframe.
> An existing C compiler made it possible without too much effort. The
> UNIX
> source was available to Universities by then. I also developed Mini-UNIX
> for the PDP11/10 (also no memory protection) in the 1976 timeframe.
> This source code was also made available to Universities, but the source
> code for LSX was not.
>
> Peter Weiner, the founder of INTERACTIVE Systems Corp.(ISC) in June
> 1977,
> the first commercial company to license UNIX source from Western
> Electric for $20,000. Binary licenses were available at the same time.
> I joined ISC in May of 1978 when ISC was the first company to offer
> UNIX support services to third parties. There was never any talk about
> licensing UNIX source code from Western Electric (WE) from the founding
> of ISC to when the Intel 8086 micro became available in 1981.
> DEC never really targeted the PC market with the LSI-11 micro,
> and WE never made it easy to license binary copies of the UNIX
> source code, So LSX never really caught on in the commercial market.
> ISC was in the business of porting the UNIX source code to other
> computers, micro to mainframe, as new computer architectures
> were developed.
>
As the author of LSX and MiniUnix, are you aware of anybody porting
them to another non PDP-11 architecture? ISC didn't do that at all, but
maybe you heard of something through the years?
Warner
[-- Attachment #2: Type: text/html, Size: 1952 bytes --]
next prev parent reply other threads:[~2021-04-07 1:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 15:35 M Douglas McIlroy
2021-04-06 17:09 ` Clem Cole
2021-04-06 17:32 ` Charles H Sauer
2021-04-06 20:11 ` Josh Good
2021-04-06 20:26 ` Jim Capp
2021-04-06 20:47 ` Charles H Sauer
2021-04-07 16:42 ` Josh Good
2021-04-07 18:04 ` Charles H. Sauer
2021-04-07 2:49 ` Dave Horsfall
2021-04-07 6:04 ` arnold
2021-04-07 16:01 ` heinz
2021-04-06 21:06 ` Clem Cole
2021-04-07 0:58 ` heinz
2021-04-07 1:37 ` Warner Losh [this message]
2021-04-07 3:38 ` Dave Horsfall
2021-04-07 2:30 ` Ed Bradford
2021-04-07 2:44 ` Charles H. Sauer
2021-04-06 20:20 ` Boyd Lynn Gerber
2021-04-06 22:41 ` Dave Horsfall
2021-04-07 1:10 ` Jon Steinhart
2021-04-07 1:47 ` Greg 'groggy' Lehey
2021-04-07 1:49 ` Jon Steinhart
2021-04-07 1:58 ` Larry McVoy
2021-04-07 2:31 ` Serge Burjak
2021-04-09 21:24 ` Michael Parson
2021-04-10 3:33 ` Ed Bradford
2021-04-10 15:12 ` Clem Cole
2021-04-10 15:41 ` Larry McVoy
2021-04-07 0:59 Jason Stevens
2021-04-10 18:12 Paul Ruizendaal via TUHS
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='CANCZdfqHg4MzgDVMmFg-xyZyJrLtHZ2b4aBGBn2vnFmm+rjy=g@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=heinz@osta.com \
--cc=tuhs@minnie.tuhs.org \
/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;
as well as URLs for NNTP newsgroup(s).