From: Peter Yardley <peter.martin.yardley@gmail.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Anyone ever heard of teaching a case study of Initial Unix?
Date: Mon, 8 Jul 2024 22:29:04 +1000 [thread overview]
Message-ID: <67F367A2-71D5-4AB8-A1AF-2DBE37F28A6C@gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2407080728410.6233@aneurin.horsfall.org>
Just a recollection …
Our department sold our Nova to the Navy (RAN) as part of a programming course on Novas and microcomputers. The Navy still used the Novas as gunnery computers, possibly amongst things, ours was going to be used for training. It had core memory, which was an advantage in the turrets of the frigates (hard drives of the time didn’t survive the shock). One of my colleagues used to fix the core memory using a magnifying loupe and a fine soldering iron.
We had Algol, ForTran and 8080 and 6502 cross assemblers amongst other things. There was a 16 user editor and you had to line up on the system console to be able to do a compilation (we were running a foreground/background OS, it was a pretty small system). We all used the same directory and had to name our files with our initials.
> On 8 Jul 2024, at 8:00 AM, Dave Horsfall <dave@horsfall.org> wrote:
>
> On Fri, 5 Jul 2024, Peter Yardley wrote:
>
>> The DG Nova had a pretty nice architecture. 2 accumulators, 2 index
>> registers, program counter, status register. No stack register tho.
>> There was a micro processor version by Fairchild.
>
> The story behind it is interesting too. The designer at DEC (Ed de
> Castro) tried to promote it, Ken Olson didn't like it, so he left to form
> Data General and created the DG Nova.
>
> OK, not a Unix box...
>
> -- Dave
.1.3.6.1.4.1.8852.4.2
Peter Yardley
peter.martin.yardley@gmail.com
next prev parent reply other threads:[~2024-07-08 12:29 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 4:51 [TUHS] " sjenkin
2024-07-03 5:02 ` [TUHS] " Al Kossow
2024-07-03 6:46 ` arnold
2024-07-03 14:04 ` Clem Cole
2024-07-03 15:22 ` Theodore Ts'o
2024-07-03 15:36 ` Larry McVoy
2024-07-03 14:59 ` Marc Rochkind
2024-07-03 23:35 ` G. Branden Robinson
2024-07-04 13:00 ` Marc Donner
2024-07-03 9:04 ` A. P. Garcia
2024-07-03 15:17 ` Vincenzo Nicosia
2024-07-03 15:35 ` Marc Donner
2024-07-03 17:39 ` Jon Forrest
2024-07-03 17:49 ` segaloco via TUHS
2024-07-03 18:16 ` Erik E. Fair
2024-07-03 19:58 ` Rich Salz
2024-07-03 23:15 ` Dave Horsfall
2024-07-03 23:23 ` Marc Donner
2024-07-03 23:26 ` Rik Farrow
2024-07-04 23:26 ` Dave Horsfall
2024-07-03 15:37 ` Al Kossow
2024-07-03 16:01 ` Al Kossow
2024-07-03 16:05 ` Warner Losh
2024-07-03 23:29 ` Marc Rochkind
2024-07-03 23:50 ` G. Branden Robinson
2024-07-04 8:23 ` Vincenzo Nicosia
2024-07-04 20:34 ` Nevin Liber
2024-07-04 20:44 ` segaloco via TUHS
2024-07-04 21:41 ` sjenkin
[not found] ` <7AC009E5-C985-44AD-A55E-E0BFC05CDD31@serissa.com>
2024-07-05 9:41 ` Steve Jenkin
2024-07-05 9:47 ` Steve Jenkin
2024-07-05 0:03 ` Stuff Received
2024-07-05 0:12 ` Larry McVoy
2024-07-05 2:24 ` Adam Thornton
2024-07-05 2:42 ` Bakul Shah via TUHS
2024-07-05 7:13 ` arnold
2024-07-05 7:42 ` Bakul Shah via TUHS
2024-07-05 8:20 ` arnold
2024-07-05 8:52 ` G. Branden Robinson
2024-07-05 7:36 ` Dave Horsfall
2024-07-05 10:18 ` Peter Yardley
2024-07-05 21:38 ` [TUHS] Re: mental architecture models, " John Levine
2024-07-05 21:49 ` Larry McVoy
2024-07-05 22:08 ` Charles H Sauer (he/him)
2024-07-05 22:24 ` Larry McVoy
2024-07-05 23:17 ` John Levine
2024-07-06 12:52 ` sjenkin
2024-07-06 14:02 ` John R Levine
2024-07-06 15:58 ` Clem Cole
2024-07-06 20:56 ` John R Levine
2024-07-06 21:32 ` Charles H Sauer (he/him)
2024-07-06 23:46 ` Peter Yardley
2024-07-07 17:43 ` James Frew
2024-07-07 1:39 ` John Levine
2024-07-07 3:26 ` [TUHS] Re: PL.8 [was " Charles H Sauer (he/him)
2024-07-08 21:39 ` [TUHS] " Aron Insinga
2024-07-08 22:14 ` Paul Winalski
2024-07-09 1:04 ` Aron Insinga
2024-07-08 22:17 ` Rik Farrow
2024-07-09 0:08 ` Adam Thornton
2024-07-09 2:40 ` Dave Horsfall
2024-07-09 2:43 ` Warner Losh
2024-07-09 4:23 ` Adam Thornton
2024-07-09 5:06 ` Aron Insinga
2024-07-07 5:33 ` arnold
2024-07-05 22:10 ` Dan Cross
2024-07-07 22:00 ` [TUHS] " Dave Horsfall
2024-07-07 23:28 ` Brad Spencer
2024-07-08 6:17 ` Dave Horsfall
2024-07-08 6:27 ` Lars Brinkhoff
2024-07-08 6:51 ` Dave Horsfall
2024-07-08 9:36 ` David Arnold
2024-07-08 6:59 ` arnold
2024-07-08 13:22 ` Larry McVoy
2024-07-08 15:37 ` Al Kossow
2024-07-08 17:22 ` Tom Lyon
2024-07-08 17:04 ` Clem Cole
2024-07-08 15:28 ` Brad Spencer
2024-07-08 15:33 ` Al Kossow
2024-07-09 22:54 ` Dave Horsfall
2024-07-10 13:18 ` Chet Ramey via TUHS
2024-07-10 14:29 ` John Levine
2024-07-08 0:21 ` John Levine
2024-07-08 0:35 ` Dave Horsfall
2024-07-08 12:29 ` Peter Yardley [this message]
2024-07-05 16:40 ` Jon Steinhart
2024-07-06 13:20 ` Dave Horsfall
2024-07-05 0:08 ` Marc Rochkind
2024-07-04 1:53 ` John Levine
2024-07-04 2:59 ` segaloco via TUHS
2024-07-04 6:53 ` Rob Pike
2024-07-04 15:07 ` Larry McVoy
2024-07-03 14:46 [TUHS] " Norman Wilson
2024-07-03 15:45 ` [TUHS] " Clem Cole
2024-07-03 15:52 ` Clem Cole
2024-07-03 16:12 ` Chet Ramey via TUHS
2024-07-05 13:20 Douglas McIlroy
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=67F367A2-71D5-4AB8-A1AF-2DBE37F28A6C@gmail.com \
--to=peter.martin.yardley@gmail.com \
--cc=dave@horsfall.org \
--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).