The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Phil Budne <>
Subject: [TUHS] Re: Early supported UNIX manual
Date: Fri, 23 Dec 2022 13:04:54 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Jonathan Gray asked:
> Is there an access() system call?


> or alarm() and pause() system calls added in the v6 "50 changes"

yes to both

> or changes to C such as libS/stdio, unsigned and typedef which would
> later show up in the compiler on the phototypesetter version 7 tape.
> usr/source/c_compiler/ on the unsw3 tape may be close to that compiler,
> it isn't the same as the pwb compiler.

The getc and putc man page synopsis look identical to the ones at

Section VI differs from

Mine has (in addition to those in v6)
	agen -- generates associative memory drivers
	hyphen -- find hyphenated words
	lex -- generate programs for simple lexical analysis
	ptx -- permuted index
	tmac -- -ms macros which is ms(vii) in v6

And from v6 is missing: azel col graph m6 plot quiz sky speak spline tbl tmg

Compared to the v7 lex, the one command line argument is "-code",
equivalent to a first input line of "%-code" which changes the output
prefix from "yy" to "code".

Compared to v6, Section I is missing: eqn, lpr, man, neqn, newgrp,
opr, rc, rev, roff, spell, tee, troff.

But has:
	lc (LIL compiler)
	mtm (magnetic tape manipulation),
	onintr (specify interrupt handling for a command file)
	read/open/onend (sequential file read)
	req (rewind tape)
	sum (sum file)

The one man page I compared is yacc(I) which is missing the '-r'
(ratfor) option present in v6

The manual is typeset, and the inside of the cover page days "This
manual was set by a Grahpic Systems phototypesetter driven by the
troff formatting program under the UNIX system.  The text of the
manual was prepared using the ed text editor"

No sign of new archive format.

I have only the manual pages, so I can't speak to the state of C.

  reply	other threads:[~2022-12-23 18:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23  2:26 Noel Chiappa
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 [this message]
  -- 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).