From owner-freebsd-hackers Sun Mar 21 23:15: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id A829F14CFC for ; Sun, 21 Mar 1999 23:15:05 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id CAA28422 for ; Mon, 22 Mar 1999 02:14:45 -0500 (EST) Message-Id: <199903220714.CAA28422@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: beyond 32 signals Date: Mon, 22 Mar 1999 02:14:45 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have periodically poked arround with moving FreeBSD beyond 32 signals. The current idea that wanders through my head every few months or so is to create a seperate set of signal routines (sigaction() and friends) for handling and registering signals (all new programs would be compiled with the newer version (new syscall #), but old programs continue to work. The problem I have come across is sigcontext (a wonderfully usefull structure) has a in for the signal mask. I cannot figure out a way to get arround this without having 2 seperate signal processing systems (I really would like to avoid that. Anyone have any ideas on this? -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message