access(2) alarm(2) pause(2) were not ported from pwb to v7
authorjsg <jsg@openbsd.org>
Tue, 2 Aug 2022 01:23:23 +0000 (01:23 +0000)
committerjsg <jsg@openbsd.org>
Tue, 2 Aug 2022 01:23:23 +0000 (01:23 +0000)
commit5d5c4c8bb7244fbd289695a1c4320e6e81c5653e
treee62d116edcfc453a81ec9a11bc650bbebb3899cf
parent48352e7ba586ecd6635a13b887330dc49cbd8d63
access(2) alarm(2) pause(2) were not ported from pwb to v7

Alan Glasser describes the incident that led to access(2) in
https://minnie.tuhs.org/pipermail/tuhs/2021-November/024657.html

access(2) alarm(2) pause(2) were also part of the "50 changes" tape

post v6 "50 bugs" / "diff tape" / "50 fixes" tape (Salus QCU, pp 138-139)
"fifty changes" tape
https://www.oreilly.com/openbook/opensources/book/kirkmck.html

"50 changes"
https://archive.org/details/unix_news_november-1976

tuhs/Applications/Spencer_Tapes/unsw3.tar.gz
usr/sys/v6unix/changenotes

45) The "access()" system call checks access permissions on the real
id's of the process regardless of the effective ones.  Doesn't return
stats, just does an internal "access()" to set u.u_error.

48) "alarm()" and "pause()" system calls are in to provide a user-mode
timeout capability.

with and ok schwarze@
lib/libc/gen/alarm.3
lib/libc/gen/pause.3
lib/libc/sys/access.2