From: Jeffrey A Law <law@cygnus.com>
To: Stan Sieler <sieler@allegro.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] HPUX binary compatibility
Date: Mon, 21 Jun 1999 12:23:12 -0600 [thread overview]
Message-ID: <14666.929989392@upchuck.cygnus.com> (raw)
In-Reply-To: Your message of Mon, 21 Jun 1999 11:07:19 PDT. <199906211807.LAA29277@bart.allegro.com>
In message <199906211807.LAA29277@bart.allegro.com>you write:
> > You really don't want to do that. I strongly recommend against it. In
>
> (Presuming "that" is "have different system call numbers")
Correct.
> You're "compatible" if you can run an HP-UX app "out of the box" (e.g.,
> restore it and run). If you have to run it through a translator of some ki
> nd,
> you aren't compatible. (If the translator is part of the OS, and invoked
> automatically & invisibly, that's ok...been there, used that for 15 years
> on MPE)
The translator is entirely in the kernel. It does not require hacking the
binary in any way shape or form.
> Without such a mechanism, you can't tell the system calls apart.
Yes you can. The exec headers have different magic #s which you can use
to identify hpux vs bsd vs osf vs lites vs linux binaries.
If the process is not a linux process, then you look up the syscall number
in the appropriate translation table. Similarly for signal #s, errno values,
etc.
I strongly recommend you actually look at the code Utah wrote. It handles
hpux compatibility well enough to run X servers, compilers, shells, etc etc
right off an hpux distribution tape/cd.
jeff
next prev parent reply other threads:[~1999-06-21 18:28 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 [this message]
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=14666.929989392@upchuck.cygnus.com \
--to=law@cygnus.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=sieler@allegro.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.