From: Larry McVoy <lm@mcvoy.com>
To: 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: Sat, 11 Feb 2023 06:48:32 -0800 [thread overview]
Message-ID: <20230211144832.GA6858@mcvoy.com> (raw)
In-Reply-To: <Y+cQ2/yG9+UWUSsg@largo.jsg.id.au>
On Sat, Feb 11, 2023 at 02:51:55PM +1100, Jonathan Gray wrote:
> http://bitsavers.org/pdf/opusSystems/32k/800-00237-000_Opus_100pm_User_Manual_1987.pdf
That gave me the best "feel" for what it was like. Still would like to
hear from someone that ran on this on a day to day basis. It looks
pretty cool but either it happened a little too late for me (by 1987
I was working for Lachman porting Unix to the ETA-10 and I was running
on Sun3/50 as my desktop and Sun3/260 as the file server) or I missed
it.
I owned an AT&T Unix PC in college (I think, or I used Rob Netzer's
but I think we had 2 of them) and it would be interesting to know
how the 320xx on an AT stacked up against that.
next prev parent reply other threads:[~2023-02-11 14:48 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
2023-02-11 0:53 ` Larry McVoy
2023-02-11 3:51 ` Jonathan Gray
2023-02-11 14:48 ` Larry McVoy [this message]
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=20230211144832.GA6858@mcvoy.com \
--to=lm@mcvoy.com \
--cc=jsg@jsg.id.au \
--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).