From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] finding help in v7 in 1980
Date: Fri, 10 Nov 2017 10:06:41 -0800 [thread overview]
Message-ID: <20171110180641.GB25370@mcvoy.com> (raw)
In-Reply-To: <0d7c61c7-7f5a-1854-64c3-737f4de1233c@gmail.com>
On Fri, Nov 10, 2017 at 12:00:15PM -0600, Will Senn wrote:
> My question for you citizens of that long-ago era :), is this - what was it
> like to sit down and learn unix V7 on a PDP? Not from a hardware or
> ergonomics perspective, but from a human information processing perspective.
> What resources did you consult in your early days and what did the workflow
> look like in practical terms.
I learned on the VAX, did some PDP-11 assembly but I dunno if I ever
ran on one. Definitely spent a lot of time on 11/750, 11/780 and the 8600.
The hardest part, for me, was learning command names. Where is dir?
Oh, it's ls. Etc.
I believe the 4BSD manuals (those ones with red/yellow/green plastic
binders) had listings of the commands with the synopsis, either they
did or someone gave such a thing. That was a big jump start.
The next thing was someone gave me an account on ..!uwvax!slovax which
was an 11/750 that had the 4.2BSD source on it. Many, many hours reading
the source and having my eyes opened.
--lm
next prev parent reply other threads:[~2017-11-10 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 18:00 Will Senn
2017-11-10 18:06 ` Larry McVoy [this message]
2017-11-10 18:12 ` Ralph Corderoy
2017-11-10 19:18 ` Chet Ramey
2017-11-10 18:18 ` Michael Kjörling
2017-11-10 18:19 ` Ralph Corderoy
2017-11-10 18:21 ` Ron Natalie
2017-11-10 19:15 ` Jon Forrest
2017-11-10 19:20 ` Ron Natalie
2017-11-10 19:47 ` William Pechter
2017-11-10 19:51 ` Bakul Shah
2017-11-11 16:46 ` Nemo
2017-11-10 18:32 Noel Chiappa
2017-11-10 19:35 ` Clem Cole
2017-11-10 22:28 ` Dave Horsfall
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=20171110180641.GB25370@mcvoy.com \
--to=lm@mcvoy.com \
/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).