Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!think.com!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn From: gwyn@smoke.brl.mil (Doug Gwyn) Newsgroups: comp.unix.questions Subject: Re: Answer on sockets; Question on screen under SunOS 4.[01] Message-ID: <14478@smoke.brl.mil> Date: 15 Nov 90 20:57:03 GMT References: <7122:Nov1408:21:1690@kramden.acf.nyu.edu> Organization: U.S. Army Ballistic Research Laboratory, APG, MD. Lines: 15 In article <7122:Nov1408:21:1690@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes: >You're seeing the evil effects of POSIX sessions, the only innovation in >P1003.1 not based upon real-world experience and hence (objectively) the >worst feature of the standard. SunOS 4.1 is a POSIX-based system. Actually, it was based on real-world experience, although as with many of the details in such standards the standard specified a slight variant of what had previously been implemented. The capsule summary: BSD job control is a horrible kludge that never did work right and required vhangup etc. HP-UX was based on UNIX System V and when customers wanted job control some reengineering was necessary in order to make it work in that environment and also to close several security holes. POSIX job control was originally specified along the lines recommended by HP-UX engineers, but got redesigned during balloting, as did lots of other stuff. I think the IEEE balloting procedures suck.