From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] pre-UNIX legacy in UNIX?
Date: Tue, 19 Dec 2017 17:26:41 -0500 [thread overview]
Message-ID: <201712192226.vBJMQfVg029760@coolidge.cs.Dartmouth.EDU> (raw)
In-Reply-To: <7wd13aa3ad.fsf@junk.nocrew.org>
>> In fact, I don't recall being aware of the existence of the ITS
>> movement at the time Unix arose.
>Was there ever a movement? It was just four machines at MIT.
I struggled over the word when I wrote it. ITS has been described
as some kind of pushback against the big (and ostensibly commerce-
oriented) Multics project. I still haven't though of a word with
really appropriate connotations.
Doug
next prev parent reply other threads:[~2017-12-19 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 18:48 Doug McIlroy
2017-12-19 20:08 ` Lars Brinkhoff
2017-12-19 22:26 ` Doug McIlroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-20 1:03 Noel Chiappa
2017-12-19 20:29 Richard Tobin
2017-12-19 6:00 Nigel Williams
2017-12-19 6:21 ` Lars Brinkhoff
2017-12-19 7:07 ` Don Hopkins
2017-12-19 18:21 ` Grant Taylor
2017-12-19 19:05 ` Ralph Corderoy
2017-12-19 20:03 ` Grant Taylor
2017-12-19 20:14 ` arnold
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=201712192226.vBJMQfVg029760@coolidge.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
/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).