The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <>
To: Phil Budne <>
Subject: [TUHS] Re: Early supported UNIX manual
Date: Thu, 22 Dec 2022 21:55:06 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Drat, the origin of SysIII init remains's not in PWB 1, now not in USG Issue 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 <> 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.

  reply	other threads:[~2022-12-22 21:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2022-12-23  2:26 [TUHS] Re: Early supported UNIX manual 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

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 \
    --in-reply-to='' \ \ \ \

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