From: Larry McVoy <lm@mcvoy.com>
To: Adam Sampson <ats@offog.org>
Cc: Alexander Jacocks via TUHS <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Photos of University Computer Labs
Date: Wed, 22 Dec 2021 18:18:05 -0800 [thread overview]
Message-ID: <20211223021805.GK24180@mcvoy.com> (raw)
In-Reply-To: <y2a8rwcyuo1.fsf@offog.org>
On Thu, Dec 23, 2021 at 01:30:38AM +0000, Adam Sampson wrote:
> Alexander Jacocks via TUHS <tuhs@minnie.tuhs.org> writes:
>
> > I???m looking for photographs of university computer labs from 1985
> > until 1995, particularly labs full of unix workstations, of
> > course. Does anyone here have photos like that in their collection?
>
> Here's a computer lab at Dundee Institute of Technology (now Abertay
> University), Dundee, Scotland around 1985:
>
> http://stuff.offog.org/dct/torch-lab-c1985.jpg
>
> It's unlikely that there was any Unix involved in that picture -- the
> Torch machines pictured are modified BBC Micros with a Z80 coprocessor
> so they can run a CP/M clone, and DIT's computer centre had a TOPS-20
> system and several VMS machines at that point.
The terminal rooms bring back memories. I learned *so* much looking
over someone else's shoulder and going "how did you make vi do that?".
The CP/M machines bring back different memories, using that and BDS
C because an 11/780 with 4MB of ram and 40 users meant each user was
getting 1KB so it swapped and swapped and swapped. 128K less the space
for video on a CP/M machine was slower when you had the VAX to yourself
(as in never) and much faster in general. Wrote a boatload of funky C
code on my CP/M machine. More lonely but more productive code wise.
--lm
next prev parent reply other threads:[~2021-12-23 2:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 15:11 Alexander Jacocks via TUHS
2021-12-22 20:31 ` josh
2021-12-22 21:07 ` Rob Pike
2021-12-22 21:15 ` Rob Pike
2021-12-23 4:28 ` Warren Toomey
2021-12-23 4:31 ` Alexander Jacocks via TUHS
2021-12-23 4:45 ` Rob Pike
2021-12-22 21:14 ` Win Treese
2021-12-23 0:48 ` Adam Thornton
2021-12-23 1:30 ` Adam Sampson
2021-12-23 2:18 ` Larry McVoy [this message]
2021-12-23 13:05 ` Michael Kjörling
2021-12-23 14:19 ` Larry McVoy
2021-12-23 15:29 ` [TUHS] Photos of University Computer Labs - now off topic Dr Iain Maoileoin
2021-12-23 16:00 ` Larry McVoy
2021-12-23 16:28 ` Dr Iain Maoileoin
2021-12-23 16:35 ` Larry McVoy
2021-12-23 16:47 ` Dr Iain Maoileoin
2021-12-23 22:15 ` Steve Nickolas
2021-12-24 20:57 ` Derek Fawcus
2021-12-23 16:02 ` Warner Losh
2021-12-23 16:19 ` Larry McVoy
2021-12-23 22:13 ` Steve Nickolas
2021-12-24 3:48 ` Theodore Ts'o
2021-12-28 21:45 ` Greg A. Woods
2021-12-29 16:58 ` Theodore Ts'o
2022-01-09 19:04 ` Stuart Remphrey
2021-12-25 0:00 ` [TUHS] Photos of University Computer Labs Mike Markowski
2021-12-29 2:44 ` Alexander Jacocks 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=20211223021805.GK24180@mcvoy.com \
--to=lm@mcvoy.com \
--cc=ats@offog.org \
--cc=tuhs@minnie.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).