Date: Tue, 31 Aug 1999 11:23:14 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Francis Jordan <frankrj@netscape.net> Cc: Marcel Moolenaar <marcel@scc.nl>, hackers@freebsd.org Subject: Re: More than 32 signals. Thought? Message-ID: <Pine.BSF.4.10.9908311122040.340-100000@salmon.nlsystems.com> In-Reply-To: <37CABABF.33E13FF@netscape.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Aug 1999, Francis Jordan wrote:
> Marcel Moolenaar wrote:
> >
> > [cc'd to David E. Cross (crossd@cs.rpi.edu) and James Raynard
> > (jraynard@freebsd.org)]
> >
> > I'm thinking about extending the number of signals. I like your thoughts
> > and opinions.
> >
> > Basicly what I'm going to do is rewrite the signalling code to use a new
> > sigset_t and provide new syscalls to use it. The current syscalls convert
> > between the current and the new types for compatibility. I think I'm going
> > to borrow a thought or two from Linux which allows further increasing of
> > the number of signals without rewriting the logic, but that's basicly
> > undecided yet and open for discussion.
>
>
> Do as NetBSD does to remain compatible? Or borrow a few thoughts from
> Solaris, which also has 128 signals:
>
> typedef struct { /* signal set type */
> unsigned long __sigbits[4];
> } sigset_t;
Please be careful with your datatypes when formulating this. If you are
going to pack 32 signals into one field, make it u_int32_t, not int or
long.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
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?Pine.BSF.4.10.9908311122040.340-100000>