The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jonathan Gray <>
To: segaloco <>
Subject: [TUHS] Re: Early supported UNIX manual
Date: Sat, 24 Dec 2022 21:30:17 +1100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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: (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.
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:

  reply	other threads:[~2022-12-24 10:30 UTC|newest]

Thread overview: 17+ 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
2022-12-24  3:30     ` Jonathan Gray
2022-12-24  8:58       ` segaloco via TUHS
2022-12-24 10:30         ` Jonathan Gray [this message]
2022-12-23  8:47 ` [TUHS] Re: Book Scanning. (Was: Early supported UNIX manual) Ralph Corderoy
2024-01-07  7:03 ` [TUHS] Re: Early supported UNIX manual Jonathan Gray
2024-01-07 10:38   ` Al Kossow
2024-01-07 15:27     ` Phil Budne
2024-01-07 17:21       ` segaloco via TUHS
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

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