From: Henry Mensch <henry@henare.com>
To: "Theodore Ts'o" <tytso@MIT.EDU>, Jonathan Gray <jsg@jsg.id.au>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: project athena (was Re: Setting up an X Development Environment for Mac OS)
Date: Fri, 10 Feb 2023 19:13:41 -0500 [thread overview]
Message-ID: <1863dd20b08.2952.27ce34798ec5af9926fa49424fa0531c@henare.com> (raw)
In-Reply-To: <Y+Rfo2QQf9vcs+l1@mit.edu>
that would have happened before I arrived in April of 1986. my first job at Athena was to. get folks off those XTs and (mostly) ATs.
This was wildly unsuccessful and unpopular because the replacement hardware wouldn't be similarly capable... and also because, even then, there were more things that could be plugged into XTs and ATs. The old platform was perceived as more versatile.
- Henry
On February 9, 2023 20:30:47 "Theodore Ts'o" <tytso@mit.edu> wrote:
> On Thu, Feb 09, 2023 at 09:12:28AM +1100, Jonathan Gray wrote:
>>
>> Before the PC/RT machines and AOS, there was also an attempt at PC/XT
>> machines with Genix running on a add-in card.
>
> It's possible that there were some IBM'ers at MIT Building E40 (where
> Project Athena was headquartered) that were playing with a PC/XT with
> a co-processor board, but as far as I know that was never deployed in
> the field --- at least, I never saw them. The only I saw were PC/AT's
> (that is, the ones with the '286 CPU) that ran DOS and which were
> essentially used only to telnet to the Vax 750's (or supdup to the MIT
> AI / LCS lab machines, but most undergraduates didn't have access to
> those computers; connecting to MIT Multics was also possible, via a
> 3270 emulator, but again, most undergrduates didn't have access,
> although MIT's Student Information Processing Board could give out
> limited accounts for undergraduates to experiment with Multics.)
>
> - Ted
next prev parent reply other threads:[~2023-02-11 0:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 1:46 [TUHS] Setting up an X Development Environment for Mac OS Will Senn
2023-01-25 7:45 ` [TUHS] " segaloco via TUHS
2023-01-25 8:00 ` Lars Brinkhoff
2023-01-25 16:41 ` Rich Salz
2023-01-25 19:53 ` Theodore Ts'o
2023-01-25 20:04 ` Dan Cross
2023-01-25 20:23 ` Larry McVoy
2023-01-25 20:27 ` Chet Ramey
2023-01-27 4:49 ` Theodore Ts'o
2023-01-27 18:05 ` Henry Mensch
2023-01-27 18:24 ` Charles H Sauer (he/him)
2023-01-26 13:17 ` Marc Donner
2023-02-08 22:12 ` [TUHS] project athena (was Re: Setting up an X Development Environment for Mac OS) Jonathan Gray
2023-02-09 2:51 ` [TUHS] " Theodore Ts'o
2023-02-11 0:13 ` Henry Mensch [this message]
2023-02-11 0:53 ` Larry McVoy
2023-02-11 3:51 ` Jonathan Gray
2023-02-11 14:48 ` Larry McVoy
2023-02-12 2:26 ` Jonathan Gray
2023-02-12 21:35 ` Henry Mensch
2023-02-11 0:23 ` Henry Mensch
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=1863dd20b08.2952.27ce34798ec5af9926fa49424fa0531c@henare.com \
--to=henry@henare.com \
--cc=jsg@jsg.id.au \
--cc=tuhs@tuhs.org \
--cc=tytso@MIT.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).