From owner-freebsd-hackers Sat Oct 21 00:09:00 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA05591 for hackers-outgoing; Sat, 21 Oct 1995 00:09:00 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA05586 for ; Sat, 21 Oct 1995 00:08:57 -0700 Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id AAA26703; Sat, 21 Oct 1995 00:08:45 -0700 Message-ID: <30889C7D.446B9B3D@FreeBSD.org> Date: Sat, 21 Oct 1995 00:08:45 -0700 From: "Jordan K. Hubbard" X-Mailer: Mozilla 2.0b1 (X11; I; FreeBSD 2.1-STABLE i386) MIME-Version: 1.0 To: John Birrell CC: Julian Elischer , hackers@FreeBSD.org, jb@cimlogic.com.au Subject: Re: NetBSD/FreeBSD (pthreads) References: <199510210233.MAA05412@werple.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org Precedence: bulk John Birrell wrote: > some of the issues we addressed. He pointed out that POSIX requires a global > set of signal handlers. I guess you'd prefer to stick as close to POSIX as > you can? We can live with a global set of signal handlers (like we do with > OSF/1). It just seemed nice to do it thread by thread. 8-(. Yes, it does. Any chance of making it a knob, so that the POSIX weenies can get the global behavior and those needing the other can have that too? Maybe a sysctl variable, set to POSIX compliance by default? -- Jordan