From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthew Wilcox <Matthew.Wilcox@genedata.com>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] HPUX binary compatibility
Date: Mon, 21 Jun 1999 10:41:48 +0200 [thread overview]
Message-ID: <19990621104148.M30362@mencheca.ch.genedata.com> (raw)
In-Reply-To: <E10vomE-0004vh-00@the-village.bc.nu>; from Alan Cox on Sun, Jun 20, 1999 at 10:05:16PM +0100
On Sun, Jun 20, 1999 at 10:05:16PM +0100, Alan Cox wrote:
> > any negative effect on anything. Where it gets a little more thorny is
> > in signal.h -- HPUX uses more than 32 signals. Is it going to negatively
> > impact Linux at all to use more than 32? I see there is space reserved
> > for them, but I'd like someone to reassure me.
>
> How many non RT signals has HP/UX got. If its more than 32 we should allow
> for it, otherwise whoever does HP/UX compatibility will hate you
1-36 are non-RT, 37-44 are RT. The header file contains the ominous
comment:
/* New signals: assign numbers before _SIGRTMIN, and increase _SIGRTMIN
and _SIGRTMAX to keep at end. */
The signal.h I committed last night gives Linux/PARISC ordinary signals
from 1-36 and RT signals from 37-64. I reused _SIGGFAULT (Graphics
framebuffer fault) to be SIGSTKFLT for which HPUX has no equivalent. My
question was, will having more than 32 signals annoy any Linux people?
--
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson
next prev parent reply other threads:[~1999-06-21 8:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-20 17:40 [parisc-linux] HPUX binary compatibility Matthew Wilcox
1999-06-20 19:45 ` Stan Sieler
1999-06-20 20:21 ` Jeffrey A Law
1999-06-21 8:50 ` Matthew Wilcox
1999-06-21 15:06 ` [parisc-linux] Assembly error: entry.S John David Anglin
1999-06-21 15:20 ` Matthew Wilcox
1999-06-21 15:27 ` John David Anglin
1999-06-21 15:42 ` Matthew Wilcox
1999-06-21 15:55 ` John David Anglin
1999-06-21 16:07 ` Matthew Wilcox
1999-06-21 16:16 ` John David Anglin
1999-06-21 16:32 ` [parisc-linux] Hack to head.S John David Anglin
1999-06-21 17:23 ` [parisc-linux] HPUX binary compatibility Stan Sieler
1999-06-21 17:48 ` Jeffrey A Law
1999-06-21 18:07 ` Stan Sieler
1999-06-21 18:23 ` Jeffrey A Law
1999-06-20 21:05 ` Alan Cox
1999-06-21 8:41 ` Matthew Wilcox [this message]
1999-06-21 10:35 ` Alan Cox
1999-06-21 21:39 ` Larry Dwyer
1999-06-22 9:45 ` Matthew Wilcox
1999-06-22 9:49 ` Alan Cox
1999-06-22 10:05 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
1999-06-21 18:20 Mike Hibler
1999-06-21 20:49 ` Stan Sieler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990621104148.M30362@mencheca.ch.genedata.com \
--to=matthew.wilcox@genedata.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=parisc-linux@thepuffingroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox