Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!aplcen!haven!adm!smoke!gwyn From: gwyn@smoke.BRL.MIL (Doug Gwyn) Newsgroups: comp.unix.wizards Subject: Re: Signals on Sys V Message-ID: <11617@smoke.BRL.MIL> Date: 16 Nov 89 00:22:16 GMT References: <1745@calvin.cs.mcgill.ca> <1989Nov13.140120.17775@hcr.uucp> <40629@wlbr.IMSD.CONTEL.COM> Reply-To: gwyn@brl.arpa (Doug Gwyn) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 15 In article <40629@wlbr.IMSD.CONTEL.COM> sms@WLV.IMSD.CONTEL.COM.UUCP (Steven M. Schultz) writes: >In article dougm@queso.ico.isc.com (Doug McCallum) writes: >>Its also too bad that the "sighold()" and "sigrelse()" calls only take >>a signal number and not a mask as with the BSD equivalents. > It does seem strange that the 2.8/2.9BSD libjobs functionality > from 1983/4 was implemented rather than the 4.2/3BSD signal > semantics. So System V has finally caught up with 2.9BSD, > congrats ;-) That's a rather pointless posting. If you check out the time frame for the SVR3 implementation, it would come as no surprise that the 4.1BSD semantics were used as the base model. Meanwhile, SVR4.0 has come out with full POSIX (IEEE 1003.1) semantics, which goes beyond 4.3BSD. I won't go into the history of the POSIX spec and why it differed from 4.2BSD, but there would valid reasons (I was there).