From: "Charles H Sauer (he/him) via TUHS" <tuhs@tuhs.org>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, coff@tuhs.org, tuhs@tuhs.org
Subject: [TUHS] Re: [COFF] SOSP 1973 [was Multics<->Unix Re: Re: History of cal(1)?
Date: Fri, 19 Sep 2025 16:59:36 -0500 [thread overview]
Message-ID: <076df8c1-1616-4224-88cc-85923f7d1735@technologists.com> (raw)
In-Reply-To: <20250919214920.55FBF18C073@mercury.lcs.mit.edu>
On 9/19/2025 4:49 PM, Noel Chiappa wrote:
> > From: Charles H Sauer
>
> > For various reasons, lack of commercial dominance, lack of source, ...,
> > there didn't seem to be any specific OS that gained mind share in the
> > O.S. community until Unix did.
>
> Before UNIX, almost all OS's were written in assembler, tying them to one
> particular vendor's machines. (Multics, although in PL/I, was so specialized
> to the Heneywell architecture it was in the same boat.) UNIX was really the
> first portable OS (at least, that I know of - am I wrong?. I suspect thatwas
> a large factor too.
>
> Noel
Emphasis on "portable," since there seemed to be so many competing
processor architectures. Charlie
--
voice: +1.512.784.7526 e-mail: sauer@technologists.com
fax: +1.512.346.5240 Web: https://technologists.com/sauer/
Facebook/Google/LinkedIn/mas.to: CharlesHSauer
next prev parent reply other threads:[~2025-09-19 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 21:49 [TUHS] Re: [COFF] SOSP 1973 [was Multics<->Unix Re: Re: History of cal(1)? Noel Chiappa via TUHS
2025-09-19 21:59 ` Charles H Sauer (he/him) via TUHS [this message]
2025-09-21 1:12 ` John Levine via TUHS
2025-09-21 5:25 ` Niklas Karlsson via TUHS
2025-09-22 12:51 ` Lars Brinkhoff via TUHS
2025-09-22 15:19 ` Phillip Harbison via TUHS
2025-09-22 15:24 ` Phillip Harbison via TUHS
2025-09-22 15:41 ` Lars Brinkhoff via TUHS
2025-09-22 16:45 ` Phillip Harbison via TUHS
2025-09-24 0:33 ` Dave Horsfall 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=076df8c1-1616-4224-88cc-85923f7d1735@technologists.com \
--to=tuhs@tuhs.org \
--cc=coff@tuhs.org \
--cc=jnc@mercury.lcs.mit.edu \
--cc=sauer@technologists.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;
as well as URLs for NNTP newsgroup(s).