From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: Early supported UNIX manual
Date: Thu, 22 Dec 2022 21:26:52 -0500 (EST) [thread overview]
Message-ID: <20221223022652.AD41018C079@mercury.lcs.mit.edu> (raw)
> From: Phil Budne
> The cover page has:
> ...
> Upper right corner:
> PA-1C300-01
> Section 1
> Issue 1, January 1976
> AT&TCo SPCS
I have a very similar manual; I got it a long time ago, and no longer recall
how I came by it. Minor difference: mine is for PD-1C301-01, and at the
bottom of the page, it says "ISSUE 1 1/30/76", followed by a prominent trade
secret notice.
TUHS has a copy of this version, here:
https://www.tuhs.org/Archive/Distributions/USDL/unix_program_description_jan_1976.pdf
The README file in that directory:
https://www.tuhs.org/Archive/Distributions/USDL/README
speculates that "this is PWB/1.0" but admits "this has not yet been
confirmed". It's not PWB1, it's stock V6. If you look at the writeup of
sys1$exec(), on pg. 39 of the PDF, you'll see it describing how arguments are
copied into a disk buffer; that right there is the tip-off. In PWB1 (whose
source we do have):
https://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/sys/sys/os/sys1.c
you'll see that PWB1 accumulates the arguments in a chunk of swap space.
V6 _does_ use a disk buffer for this:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V6/usr/sys/ken/sys1.c
So this is for V6.
Noel
next reply other threads:[~2022-12-23 2:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 2:26 Noel Chiappa [this message]
2022-12-23 4:32 ` Phil Budne
2022-12-23 7:52 ` arnold
2022-12-23 9:09 ` Jonathan Gray
2022-12-23 18:04 ` Phil Budne
-- strict thread matches above, loose matches on Subject: below --
2022-12-22 18:52 [TUHS] " Phil Budne
2022-12-22 19:51 ` [TUHS] " segaloco via TUHS
2022-12-22 21:44 ` Phil Budne
2022-12-22 21:55 ` segaloco via TUHS
2022-12-24 3:30 ` Jonathan Gray
2022-12-24 8:58 ` segaloco via TUHS
2022-12-24 10:30 ` Jonathan Gray
2024-01-07 7:03 ` Jonathan Gray
2024-01-07 10:38 ` Al Kossow
2024-01-07 15:27 ` Phil Budne
2024-01-07 17:21 ` segaloco 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=20221223022652.AD41018C079@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--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).