The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
* [TUHS] Early supported UNIX manual
@ 2022-12-22 18:52 Phil Budne
  2022-12-22 19:51 ` [TUHS] " segaloco via TUHS
  2022-12-23  8:47 ` [TUHS] Re: Book Scanning. (Was: Early supported UNIX manual) Ralph Corderoy
  0 siblings, 2 replies; 8+ messages in thread
From: Phil Budne @ 2022-12-22 18:52 UTC (permalink / raw)
  To: tuhs

Rather than increase subject drift on a thread I started
"UNIX on (not quite bare) System/370", here's a new thread.

Since the TUHS archive seems to now include documentation,
I decided to take a look and see if the earliest UNIX manual I have
is in the archive:

It was given to me by a friend at Stevens Tech in Hoboken NJ (c. 1980)
who had graduated, and worked for AT&T.

It's hole punched for a four ring binder
(I found an unused Bell System Project Telstar binder to put it in).

The cover page has:

Upper left corner:
Bell Telephone Laboratories Incorperated
PROGRAM APPLICATION INSTRUCTION

Upper right corner:
PA-1C300-01
Section 1
Issue 1, January 1976
AT&TCo SPCS

Center:
UNIX PROGRAMMER'S MANUAL
Program Generic PG-1C300 Issue 2
Published by the UNIX Support Group
January, 1976

The preface starts with:

This document is published as part of the UNIX Operating System Program Generic,
PG-1C300 Issue 2.  The development of the Program Generic is the result of the
efforts of the members of the UNIX Support Group, supervised by J.F. Maranzano
and composed of: R. B. Brant, J. Feder, C. D. Perez. T. M. Raleigh, R. E. Swift,
G. C. Vogel and I. A. Winheim.

and ends with

For corrections and comments please contact C. D. Perez, MH 2C-423, Extension
6041.

Not knowing who else I could ask, I brought it to a Boston Usenix (in
the 90's or oughts), and asked DMR if he could identify it.  He said
it was an early supported UNIX, and he signed the preface page for me.

The manual has sections I through VIII; all manual pages start with page -1-

I found https://www.tuhs.org/Archive/Distributions/USDL/unix_program_description_jan_1976.pdf

with cover page:
	UNIX PROGRAM DESCRIPTION
	Program Generic PG-1C300 Issue 2
	Published by the UNIX Support Group
	January 1976

contents:
	NUMBER		ISSUE	TITLE
	PD-1C301-01	1	Operating System
	PD-1C302-01	1	Device Drivers Section 1
	PD-1C303-01	1	Device Drivers Section 2

And consists of descriptions of kernel functions.

So it seems likely that my manual is a companion to that.

I have a Brother printer/scanner, but the paper is fragile, so unless
it's of immediate and burning value to someone, it's unlikely to rise
to the top of my ever-static list of documents to scan....

But if someone has specific questions I can look up, let me know....

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [TUHS] Re: Early supported UNIX manual
  2022-12-22 18:52 [TUHS] Early supported UNIX manual Phil Budne
@ 2022-12-22 19:51 ` segaloco via TUHS
  2022-12-22 21:44   ` Phil Budne
  2022-12-23  8:47 ` [TUHS] Re: Book Scanning. (Was: Early supported UNIX manual) Ralph Corderoy
  1 sibling, 1 reply; 8+ messages in thread
From: segaloco via TUHS @ 2022-12-22 19:51 UTC (permalink / raw)
  To: Phil Budne; +Cc: tuhs

That is exciting news and I wish you all the best with scanning efforts!

One area of immediate curiosity for me is the init system, whether the pages suggest it is more in line with research (rc and ttys files) or TS (inittab, runlevels).

- Matt G.

------- Original Message -------
On Thursday, December 22nd, 2022 at 10:52 AM, Phil Budne <phil@ultimate.com> wrote:


> Rather than increase subject drift on a thread I started
> "UNIX on (not quite bare) System/370", here's a new thread.
> 
> Since the TUHS archive seems to now include documentation,
> I decided to take a look and see if the earliest UNIX manual I have
> is in the archive:
> 
> It was given to me by a friend at Stevens Tech in Hoboken NJ (c. 1980)
> who had graduated, and worked for AT&T.
> 
> It's hole punched for a four ring binder
> (I found an unused Bell System Project Telstar binder to put it in).
> 
> The cover page has:
> 
> Upper left corner:
> Bell Telephone Laboratories Incorperated
> PROGRAM APPLICATION INSTRUCTION
> 
> Upper right corner:
> PA-1C300-01
> Section 1
> Issue 1, January 1976
> AT&TCo SPCS
> 
> Center:
> UNIX PROGRAMMER'S MANUAL
> Program Generic PG-1C300 Issue 2
> Published by the UNIX Support Group
> January, 1976
> 
> The preface starts with:
> 
> This document is published as part of the UNIX Operating System Program Generic,
> PG-1C300 Issue 2. The development of the Program Generic is the result of the
> efforts of the members of the UNIX Support Group, supervised by J.F. Maranzano
> and composed of: R. B. Brant, J. Feder, C. D. Perez. T. M. Raleigh, R. E. Swift,
> G. C. Vogel and I. A. Winheim.
> 
> and ends with
> 
> For corrections and comments please contact C. D. Perez, MH 2C-423, Extension
> 6041.
> 
> Not knowing who else I could ask, I brought it to a Boston Usenix (in
> the 90's or oughts), and asked DMR if he could identify it. He said
> it was an early supported UNIX, and he signed the preface page for me.
> 
> The manual has sections I through VIII; all manual pages start with page -1-
> 
> I found https://www.tuhs.org/Archive/Distributions/USDL/unix_program_description_jan_1976.pdf
> 
> with cover page:
> UNIX PROGRAM DESCRIPTION
> Program Generic PG-1C300 Issue 2
> Published by the UNIX Support Group
> January 1976
> 
> contents:
> NUMBER ISSUE TITLE
> PD-1C301-01 1 Operating System
> PD-1C302-01 1 Device Drivers Section 1
> PD-1C303-01 1 Device Drivers Section 2
> 
> And consists of descriptions of kernel functions.
> 
> So it seems likely that my manual is a companion to that.
> 
> I have a Brother printer/scanner, but the paper is fragile, so unless
> it's of immediate and burning value to someone, it's unlikely to rise
> to the top of my ever-static list of documents to scan....
> 
> But if someone has specific questions I can look up, let me know....

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [TUHS] Re: Early supported UNIX manual
  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
  0 siblings, 2 replies; 8+ messages in thread
From: Phil Budne @ 2022-12-22 21:44 UTC (permalink / raw)
  To: segaloco, phil; +Cc: tuhs


Matt G wrote:
> One area of immediate curiosity for me is the init system, whether the pages suggest it is more in line with research (rc and ttys files) or TS (inittab, runlevels).

The init (VII) page mentions /etc/rc and refers to ttys (V) which says the file
consists of lines with three characters (enable, tty name, getty arg)

getty (VII) describes behaviors for 0, -, 1, 2

The one interesting bit in section (II) is lock (system call 62.) that
implements semaphores with subfunctions lock/unlock/tlock, all of
which take a non-negative semaphore ID called a flag.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [TUHS] Re: Early supported UNIX manual
  2022-12-22 21:44   ` Phil Budne
@ 2022-12-22 21:55     ` segaloco via TUHS
  2022-12-24  3:30     ` Jonathan Gray
  1 sibling, 0 replies; 8+ messages in thread
From: segaloco via TUHS @ 2022-12-22 21:55 UTC (permalink / raw)
  To: Phil Budne; +Cc: tuhs

Drat, the origin of SysIII init remains obscure...it's not in PWB 1, now not in USG Issue 2...so either PWB2, USG Issue 3 (or later) or UNIX/TS.....or maybe it's an older CB variant...anywho thank you for the quick response!

- Matt G.

------- Original Message -------
On Thursday, December 22nd, 2022 at 1:44 PM, Phil Budne <phil@ultimate.com> wrote:


> Matt G wrote:
> 
> > One area of immediate curiosity for me is the init system, whether the pages suggest it is more in line with research (rc and ttys files) or TS (inittab, runlevels).
> 
> 
> The init (VII) page mentions /etc/rc and refers to ttys (V) which says the file
> consists of lines with three characters (enable, tty name, getty arg)
> 
> getty (VII) describes behaviors for 0, -, 1, 2
> 
> The one interesting bit in section (II) is lock (system call 62.) that
> implements semaphores with subfunctions lock/unlock/tlock, all of
> which take a non-negative semaphore ID called a flag.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [TUHS] Re: Book Scanning.  (Was: Early supported UNIX manual)
  2022-12-22 18:52 [TUHS] Early supported UNIX manual Phil Budne
  2022-12-22 19:51 ` [TUHS] " segaloco via TUHS
@ 2022-12-23  8:47 ` Ralph Corderoy
  1 sibling, 0 replies; 8+ messages in thread
From: Ralph Corderoy @ 2022-12-23  8:47 UTC (permalink / raw)
  To: Phil Budne; +Cc: tuhs

Hi Phil,

> I have a Brother printer/scanner, but the paper is fragile

There are book scanners which take photographs of the pages at a
distance, typically with the manual turning of pages.  Or cradles which
hold the book and the mobile phone that does the snapping.  Or just
mobile-phone apps leaving the lighting and physical positioning up to
you.  Removing page curvature is done in software.

https://diybookscanner.org may be useful, especially its forum.
Or perhaps there's experience with ‘photo scanning’ on this list.

-- 
Cheers, Ralph.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [TUHS] Re: Early supported UNIX manual
  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
  1 sibling, 1 reply; 8+ messages in thread
From: Jonathan Gray @ 2022-12-24  3:30 UTC (permalink / raw)
  To: Phil Budne; +Cc: segaloco, tuhs

On Thu, Dec 22, 2022 at 04:44:32PM -0500, Phil Budne wrote:
> 
> Matt G wrote:
> > One area of immediate curiosity for me is the init system, whether the pages suggest it is more in line with research (rc and ttys files) or TS (inittab, runlevels).
> 
> The init (VII) page mentions /etc/rc and refers to ttys (V) which says the file
> consists of lines with three characters (enable, tty name, getty arg)
> 
> getty (VII) describes behaviors for 0, -, 1, 2
> 
> The one interesting bit in section (II) is lock (system call 62.) that
> implements semaphores with subfunctions lock/unlock/tlock, all of
> which take a non-negative semaphore ID called a flag.

used by MERT:

https://www.tuhs.org/Archive/Documentation/Manuals/MERT_Release_0/Unix%20Programmer%20Manual%20-%20UPM%20-%20White%20Tabs/System%20Calls%20-%20man2/lock.2.pdf

"The semaphores provided in the MERT/UNIX supervisor are identical to
those provided by the USG-UNIX Generic 3 system [8].
[8] Brandt, R. B., Implementation of Semaphores and Messages in UNIX, MF-76-8234-076."
https://www.tuhs.org/Archive/Documentation/TechReports/Heinz_Tech_Memos/TM-78-3114-4_The_MERT-UNIX_Supervisor_19780420.pdf

"Make (a program for maintaining other programs) was launched at the
CSRC towards the end of the year and was immediately adopted by USG for
the next generic release (PG-1C300 issue 2).  This was a snapshot of the
USG system at mod level 3.33 (January 1976) indicating at least three
distinct levels of evolution: the generic releases, major and minor USG
mod levels."

"Generic 3.0 was released in spring 1977 (delayed from January)."

Pirzada, A Statistical Examination of The Evolution of the UNIX System

"I do remember a conversation with Dennis about semaphores, though. 
He mentioned that no less than five groups inside of Bell Labs had
hacked semaphores into the kernel.  Each group did it differently."
Steve Johnson
https://minnie.tuhs.org/pipermail/tuhs/2017-February/009748.html

In CB-UNIX there was sema(2):
https://www.tuhs.org/Archive/Distributions/USDL/CB_Unix/cbunix_man2_04.pdf

In System V Release 1, semctl(2), semget(2), semop(2)
http://www.bitsavers.org/pdf/att/unix/System_V_Release_1/301-905_UNIX_System_V_Release_1_Users_Manual_Jan83.pdf

xenix creatsem(2), opensem(2), sigsem(2), waitsem(2)
http://www.bitsavers.org/pdf/intel/system3xx/xenix-286/174385-001_Overview_of_the_XENIX_286_Operating_System_Nov84.pdf

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [TUHS] Re: Early supported UNIX manual
  2022-12-24  3:30     ` Jonathan Gray
@ 2022-12-24  8:58       ` segaloco via TUHS
  2022-12-24 10:30         ` Jonathan Gray
  0 siblings, 1 reply; 8+ messages in thread
From: segaloco via TUHS @ 2022-12-24  8:58 UTC (permalink / raw)
  To: Jonathan Gray; +Cc: tuhs

Your reference to sema(2) in CB-UNIX prompted me to go check the source and curiously, that isn't in sysent.c:  https://www.tuhs.org/Archive/Distributions/USDL/CB_Unix/SourceCode/cbunix6.pdf (p. 50).  However, there is a sys5.c with some semaphore stuff in it.  Not how the code gets from the sigcall entry to that file, maybe there's a CB-specific syscall aggregator like the sys3b systemcall for 3B20-specific stuff.  It had never actually occurred to me that the semaphores in SVR1 weren't the ones from CB-UNIX, I thought they just forklifted all the IPC into 4.0 from CB.  That then means the semaphores that carried through in System V originated at least in UNIX/TS 4.0, but not by way of CB.  Minor trivia, but that's news to me.  Maybe the sysV modification request logs can shed some light, I remember seeing several IPC mentions in there.

- Matt G.

------- Original Message -------
On Friday, December 23rd, 2022 at 7:30 PM, Jonathan Gray <jsg@jsg.id.au> wrote:


> On Thu, Dec 22, 2022 at 04:44:32PM -0500, Phil Budne wrote:
> 
> > Matt G wrote:
> > 
> > > One area of immediate curiosity for me is the init system, whether the pages suggest it is more in line with research (rc and ttys files) or TS (inittab, runlevels).
> > 
> > The init (VII) page mentions /etc/rc and refers to ttys (V) which says the file
> > consists of lines with three characters (enable, tty name, getty arg)
> > 
> > getty (VII) describes behaviors for 0, -, 1, 2
> > 
> > The one interesting bit in section (II) is lock (system call 62.) that
> > implements semaphores with subfunctions lock/unlock/tlock, all of
> > which take a non-negative semaphore ID called a flag.
> 
> 
> used by MERT:
> 
> https://www.tuhs.org/Archive/Documentation/Manuals/MERT_Release_0/Unix Programmer Manual - UPM - White Tabs/System Calls - man2/lock.2.pdf
> 
> "The semaphores provided in the MERT/UNIX supervisor are identical to
> those provided by the USG-UNIX Generic 3 system [8].
> [8] Brandt, R. B., Implementation of Semaphores and Messages in UNIX, MF-76-8234-076."
> https://www.tuhs.org/Archive/Documentation/TechReports/Heinz_Tech_Memos/TM-78-3114-4_The_MERT-UNIX_Supervisor_19780420.pdf
> 
> "Make (a program for maintaining other programs) was launched at the
> CSRC towards the end of the year and was immediately adopted by USG for
> the next generic release (PG-1C300 issue 2). This was a snapshot of the
> USG system at mod level 3.33 (January 1976) indicating at least three
> distinct levels of evolution: the generic releases, major and minor USG
> mod levels."
> 
> "Generic 3.0 was released in spring 1977 (delayed from January)."
> 
> Pirzada, A Statistical Examination of The Evolution of the UNIX System
> 
> "I do remember a conversation with Dennis about semaphores, though.
> He mentioned that no less than five groups inside of Bell Labs had
> hacked semaphores into the kernel. Each group did it differently."
> Steve Johnson
> https://minnie.tuhs.org/pipermail/tuhs/2017-February/009748.html
> 
> In CB-UNIX there was sema(2):
> https://www.tuhs.org/Archive/Distributions/USDL/CB_Unix/cbunix_man2_04.pdf
> 
> In System V Release 1, semctl(2), semget(2), semop(2)
> http://www.bitsavers.org/pdf/att/unix/System_V_Release_1/301-905_UNIX_System_V_Release_1_Users_Manual_Jan83.pdf
> 
> xenix creatsem(2), opensem(2), sigsem(2), waitsem(2)
> http://www.bitsavers.org/pdf/intel/system3xx/xenix-286/174385-001_Overview_of_the_XENIX_286_Operating_System_Nov84.pdf

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [TUHS] Re: Early supported UNIX manual
  2022-12-24  8:58       ` segaloco via TUHS
@ 2022-12-24 10:30         ` Jonathan Gray
  0 siblings, 0 replies; 8+ messages in thread
From: Jonathan Gray @ 2022-12-24 10:30 UTC (permalink / raw)
  To: segaloco; +Cc: tuhs

On Sat, Dec 24, 2022 at 08:58:06AM +0000, segaloco via TUHS wrote:
> Your reference to sema(2) in CB-UNIX prompted me to go check the source and curiously, that isn't in sysent.c:  https://www.tuhs.org/Archive/Distributions/USDL/CB_Unix/SourceCode/cbunix6.pdf (p. 50).  However, there is a sys5.c with some semaphore stuff in it.  Not how the code gets from the sigcall entry to that file, maybe there's a CB-specific syscall aggregator like the sys3b systemcall for 3B20-specific stuff.  It had never actually occurred to me that the semaphores in SVR1 weren't the ones from CB-UNIX, I thought they just forklifted all the IPC into 4.0 from CB.  That then means the semaphores that carried through in System V originated at least in UNIX/TS 4.0, but not by way of CB.  Minor trivia, but that's news to me.  Maybe the sysV modification request logs can shed some light, I remember seeing several IPC mentions in there.
> 
> - Matt G.

https://www.tuhs.org/Archive/Distributions/USDL/CB_Unix/cbunix_man2L_01.pdf
describes 'EVENT:O(2L), event - semaphore operations',
event() is system call 63 in cbunix6.pdf sysent

USG UNIX 4.0 and 4.1 IPC were not the same:
https://groups.google.com/g/net.unix/c/-H9x36DMOBQ/m/4mcL76lKbmMJ

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2022-12-24 10:30 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-22 18:52 [TUHS] Early supported UNIX manual 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
2022-12-23  8:47 ` [TUHS] Re: Book Scanning. (Was: Early supported UNIX manual) Ralph Corderoy

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