The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Rich Salz <rich.salz@gmail.com>
Cc: segaloco <segaloco@protonmail.com>, TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Setting up an X Development Environment for Mac OS
Date: Wed, 25 Jan 2023 14:53:30 -0500	[thread overview]
Message-ID: <Y9GIus/Iw21uvkFb@mit.edu> (raw)
In-Reply-To: <CAFH29trXu_SGp-7xv6xqMc49tTeEuyJdKwP-Fyfe6BCrpGZ9nQ@mail.gmail.com>

On Wed, Jan 25, 2023 at 11:41:12AM -0500, Rich Salz wrote:
> > Aa for the questions of the UNIX-ness of X, it started in Athena, which as
> > I understand it was supposed to be relatively OS-agnostic distributed
> > computing? In any case, the predecessor ran on a different OS, not sure how
> > significant that is to the genesis of what would be called X or what OS it
> > "started" on.
> 
> Athena was about scaling up Unix workstations. It was started with grants
> from IBM and Digital. It was never OS-agnostic.

Well..... technically Athena was about computing in higher ed.  If you
go far back enough, at the very beginning, we used VAX 750's and IBM
PC/AT's running DOS.  As soon as the Microvax 2's and IBM PC/RT's came
in, about 2 or so years in, Project Athena switched to Unix
workstations, but in the earliest days (which would have been pre-X
Windows), Project Athena had not yet standardized on Unix or
workstations for that matter.

The VAX 750's were huge time-sharing systems that you could connect to
via VT-100's and VS-100 that were hard-wired to the VAX 750's, and
telnet from IBM PC/AT's.  The smaller clusters used PC/AT's because
they were more flexible as to which 750 you were connecting to;
otherwise, undergraduates had to go to the right terminal room in the
right part of campus to connect to the Vax 750 that you were assgined
to based on the starting character of your last name.  (And graduate
students initially didn't have access to Project Athena at all;
although if you were in EECS, LCS or the AI Lab you had access to
dedicated systems, of course.)

One of the perks for being hired as a student systems programmer back
then was that you got accounts on all of the Vax 750's, so you could
use any terminal room across campus.  :-) We then would either rlogin
to our "home" Vax 750, or we had scripts that would replicate our home
directories across the various 750's.

There was a brief, shining moment that we were standardized on
BSD-derived Unix systems, but then IBM turned down AOS (the "academic"
operating system), and we were forced to use AIX on the IBM RT's, with
all that this implied: SMIT, and other horrors.

"AIX: it *reminds* you of Unix...." was the saying at the time ---
although we tried not to say that when the IBM engineers assigned
Athena were in hearing range :-).  The one saving grace of the IBM
RT's was that they were three MIPS machines, while the Microvax's were
but a single MIPS, and that made a huge different if you were running
TeX or LaTeX.

Cheers,

						- Ted

  reply	other threads:[~2023-01-25 19:54 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25  1:46 [TUHS] " 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 [this message]
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
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
2023-01-25 20:38 [TUHS] Re: Setting up an X Development Environment for Mac OS Noel Chiappa
2023-01-25 21:25 ` Clem Cole
2023-01-26  6:30   ` Lars Brinkhoff
2023-01-26 10:56     ` Ralph Corderoy
2023-01-26 12:01       ` arnold
2023-01-26 13:25         ` Lars Brinkhoff
2023-01-26 15:28       ` [TUHS] " josh
2023-01-26 16:07         ` [TUHS] " segaloco via TUHS
2023-01-26 16:48           ` emanuel stiebler
2023-01-26 21:19             ` segaloco via TUHS
2023-01-26 22:51               ` Andy Kosela
2023-01-27  0:48                 ` segaloco via TUHS
2023-01-27  4:07                   ` Will Senn
2023-01-27 14:08                     ` Chet Ramey
2023-01-27 14:49                       ` Ron Natalie
2023-01-27 15:53                     ` Dan Cross
2023-01-27 14:17             ` Ralph Corderoy
2023-01-27 13:56         ` Ralph Corderoy
2023-01-27 14:54           ` Ron Natalie
2023-01-27 16:10             ` Larry McVoy
2023-01-28 22:15               ` Dave Horsfall
2023-01-29  0:31                 ` Kevin Bowling
2023-01-29 11:07                   ` emanuel stiebler
2023-01-27 21:42             ` Tom Perrine
2023-01-28  2:18               ` Larry McVoy
2023-01-28  2:49                 ` Tom Perrine
2023-01-26  6:32 ` Lars Brinkhoff
2023-01-26  9:45 ` emanuel stiebler 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=Y9GIus/Iw21uvkFb@mit.edu \
    --to=tytso@mit.edu \
    --cc=rich.salz@gmail.com \
    --cc=segaloco@protonmail.com \
    --cc=tuhs@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).