posix vs sys v shm/sem

Errare est humanum. Any typos, inaccuracies, editorial mistakes, big or small - please post here.

posix vs sys v shm/sem

Postby morpheus » Thu Aug 08, 2019 7:42 am

EEK. Somehow in Chapter 3 (File descriptors in Darwin), I referred to System V IPC (shmat/shmdt/smget) and Semaphores (semget/semop/semctl) as POSIX, by quoting the wrong syscall numbers! This is, of course, a mistake of mine - The Sys V IPC objects are not descriptors, and the POSIX objects use different syscalls (shm_open/unlink, sem_*...).
I saved myself 0.01BTC by catching it in this update, which also ties better now to Volume II, where I ended up expanding on their in-kernel representation.
morpheus
Site Admin
 
Posts: 723
Joined: Thu Apr 11, 2013 6:24 pm

Re: posix vs sys v shm/sem

Postby gsn » Sun Aug 11, 2019 11:07 pm

How dare you.

If we're going there,
Code: Select all
shm_open
and friends are from the POSIX realtime extension, not core POSIX.
gsn
 
Posts: 2
Joined: Sun Apr 16, 2017 11:04 pm

Re: posix vs sys v shm/sem

Postby morpheus » Wed Aug 14, 2019 2:00 am

*sigh*

(good point, though, and since I haven't printed the edition yet, I'll add realtime ext)
morpheus
Site Admin
 
Posts: 723
Joined: Thu Apr 11, 2013 6:24 pm


Return to Errata

Who is online

Users browsing this forum: No registered users and 0 guests

cron