Date: Mon, 22 Mar 1999 14:12:00 -0800 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: "David E. Cross" <crossd@cs.rpi.edu>, freebsd-hackers@FreeBSD.ORG Subject: Re: beyond 32 signals Message-ID: <199903222212.OAA17322@salsa.gv.tsc.tdk.com> In-Reply-To: "David E. Cross" <crossd@cs.rpi.edu> "beyond 32 signals" (Mar 22, 2:14am)
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 22, 2:14am, "David E. Cross" wrote: } Subject: beyond 32 signals } 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? I believe NetBSD now handles more than 32 signals. You might want to look at their implementation. --- Truck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903222212.OAA17322>