From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] HPUX binary compatibility
Date: Sun, 20 Jun 1999 19:40:15 +0200 [thread overview]
Message-ID: <19990620194015.J30362@mencheca.ch.genedata.com> (raw)
How far do we want to or are we able to go with making constants identical
between HPUX and Linux?
Some syscalls are going to have to be different between the two OSes --
ioctl is the obvious example -- but it would be nice to have to do as
little work as possible.
I've just been through errno.h making the Linux error numbers the same as
the HPUX ones. This seems pretty sane; I can't imagine that it will have
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.
The real thing which bothers me about this is that doing this means that
HPUX and Linux are then allocating from the same numberspace, so where
Linux has things which HPUX doesn't, HPUX might later allocate the same
number for a different extension.
(Of course, if HP want to add Linux binary compatibility to HPUX, now
would be a great time to mention it :-)
--
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 reply other threads:[~1999-06-20 17:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-20 17:40 Matthew Wilcox [this message]
1999-06-20 19:45 ` [parisc-linux] HPUX binary compatibility 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
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=19990620194015.J30362@mencheca.ch.genedata.com \
--to=matthew.wilcox@genedata.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.