From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: coff@tuhs.org, crossd@gmail.com
Cc: jnc@mercury.lcs.mit.edu
Subject: [COFF] Re: [TUHS] Fwd: How did Bell Labs start to work on Project MAC?
Date: Tue, 24 Jan 2023 13:47:38 -0500 (EST) [thread overview]
Message-ID: <20230124184738.5564518C080@mercury.lcs.mit.edu> (raw)
> From: Dan Cross
> From Acceptable Name <metta.crawler@gmail.com>:
Gmail has decided this machine is a source of spam, and is rejecting all email
from it, and I have yet to sort out what's going on, so someone might want to
forward anything I turn up to this person.
>> Did Bell Labs approach MIT or was it the other way around?
I looked around the Multics site, but all I could find is this: "Bell
Laboratories (BTL) joined the Multics software development effort in November
of 1964"
https://multicians.org/history.html
I did look through IEEE Annals of the History of Computing, vol. 14, no. 2,
listed there, but it's mostly about the roots of CTSS. It does have a footnote
referring to Doug, about the timing, but no detail of how Bell Labs got
involved.
I have yet to look at the oral history things from Corby, etc which may answer
this in passing.
I'll ask Jerry Saltzer if he remembers; he's about the only person left from
MIT who was around at that point.
>> Did participating in Project MAC come from researchers requesting
>> management at Bell Labs/MIT
At MIT, the 'managers' and the researchers were the same people, pretty much.
If you read the panel transcript in V14N2, Fano was the closest thing to a
manager (although he was really a professor) there was at MIT, and he talks
about not wanting to be involved in managing the thing!
Noel
next reply other threads:[~2023-01-24 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 18:47 Noel Chiappa [this message]
2023-01-24 21:09 Noel Chiappa
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=20230124184738.5564518C080@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=coff@tuhs.org \
--cc=crossd@gmail.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).