The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: reed@reedmedia.net
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] V6 networking & alarm syscall
Date: Fri, 11 Jan 2019 16:08:25 -0600 (CST)	[thread overview]
Message-ID: <alpine.NEB.2.21.1901111528210.21728@t1.m.reedmedia.net> (raw)
In-Reply-To: <CAC20D2Ni4jvA9POZKaQx6O_Dq=Nq5TfdLgbr__oWgrXme=+GHg@mail.gmail.com>

On Fri, 11 Jan 2019, Clem Cole wrote:

> Right and select(2) was created by Sam and wnj during the 4.2 development.?
> I've forgotten which sub-version (it was in 4.1c, but it might have been in
> b or a before that).? There was a lot of arguing at the time about it's need;?
> the multiple process solution was considered more 'Unix-like.'
...

I search through the SCCS code in 4.1c. There is a reference to it by 
name for 4.1a in syscalls.c (82/11/13) to answer your comment.

"#38 -- 4.1a select",   /*  38 = nosys */

The select system call was added in 81/02/07 with no comment. Commit 
history shows in 81/10/17: "cleanup (mpx removal, old tty removal, 
beginnings of select)" and in 81/10/11 "first boot with select()" which 
includes lots of changes like replace lots of tty code and use 
selwakeup().

But I don't see any of the select code itself until a new file 
kern_descrip.c was introduced in 82/07/15. Soon after the #38 select 
became obsoleted oselect and a new syscall number #93 was assigned.
(In 4.2 the select code was in sys_generic.c.)

Can someone tell me about SCCS behaviour when renaming/moving or 
deleting files? In particular, I think the select() code prior to 
82/07/15 had different source filenames that no longer exist and the 
SCCS history was lost.  Anyone else have ideas about this?  I have 
noticed this with other SCCS spelunking where code was removed and then 
corresponding "s" files were missing -- but maybe that is just the way 
the systems that our current snapshots (McKusick discs) of this history 
were made from. Maybe sccs didn't checkout the history of deleted files 
by default (that is my guess).

  parent reply	other threads:[~2019-01-11 22:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 23:12 Paul Ruizendaal
2019-01-11  0:17 ` Clem cole
2019-01-11 15:33 ` ron
2019-01-11 18:45   ` Clem Cole
2019-01-11 19:06     ` David
2019-01-11 22:08     ` reed [this message]
2019-01-11 22:18       ` Larry McVoy
2019-01-12 12:04         ` reed
2019-01-12 17:20           ` Clem Cole
2019-01-12 18:16             ` Eric Allman
2019-01-13  1:16               ` Madeline Autumn-Rose
2019-01-11 22:47       ` Clem Cole
2019-01-11 22:55         ` Eric Allman
2019-01-11 23:32         ` Warner Losh
2019-01-11 23:27 Paul Ruizendaal
2019-01-12  1:24 Noel Chiappa
2019-01-12  1:58 ` Dave Horsfall
2019-01-12  2:33   ` Warner Losh
2019-01-12  4:14 Noel Chiappa
     [not found] <mailman.1.1547258402.6716.tuhs@minnie.tuhs.org>
2019-01-12 11:13 ` Paul Ruizendaal
2019-01-13 10:52 Paul Ruizendaal
2019-01-13 15:39 ` Warner Losh

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=alpine.NEB.2.21.1901111528210.21728@t1.m.reedmedia.net \
    --to=reed@reedmedia.net \
    --cc=tuhs@minnie.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).