From: Jeffrey A Law <law@cygnus.com>
To: Matthew Wilcox <Matthew.Wilcox@genedata.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] HPUX binary compatibility
Date: Sun, 20 Jun 1999 14:21:36 -0600 [thread overview]
Message-ID: <20550.929910096@upchuck.cygnus.com> (raw)
In-Reply-To: Your message of Sun, 20 Jun 1999 19:40:15 +0200. <19990620194015.J30362@mencheca.ch.genedata.com>
In message <19990620194015.J30362@mencheca.ch.genedata.com>you write:
>
> How far do we want to or are we able to go with making constants identical
> between HPUX and Linux?
We never bothered at the UofU. It didn't seem worth the headache to try and
get either HP or Berkeley to change syscall, errno or other constants.
> 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.
Just write translators on the hpux emulation side.
ie, consider the linux values the canonical internal form.
You then have two external representations.
First is linux. Do nothing here since the internal & external representation
is the same.
Second is hpux. Translate values as you enter/exit the kernel. So for
example, you may need a second syscall table to do handoff of syscalls
after translating the syscall #. On the exit path you probably need to
translate errno values. Similarly for signals.
jeff
next prev parent reply other threads:[~1999-06-20 20:26 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 [this message]
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=20550.929910096@upchuck.cygnus.com \
--to=law@cygnus.com \
--cc=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.