From: Stan Sieler <sieler@allegro.com>
To: mike@fast.cs.utah.edu (Mike Hibler)
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] HPUX binary compatibility
Date: Mon, 21 Jun 1999 13:49:43 -0700 (PDT) [thread overview]
Message-ID: <199906212049.NAA32096@bart.allegro.com> (raw)
In-Reply-To: <199906211820.MAA06267@fast.cs.utah.edu> from "Mike Hibler" at Jun 21, 99 12:20:14 pm
Re:
> Yow, that is an ambitious goal! I can see the desirability of doing it
Yes...I've been trying to get MPE/iX to support HP-UX binaries via this
method for a number of years, but HP hasn't shown much interest.
The reason I like it is that it removes the slightly obscene distinction
of a "linux process" vs. "HP-UX process".
(MPE/iX, which also runs on PA-RISC, and which has an internal emulator
for the Classic (CISC) HP 3000 instruction set, was originally going to
have a similar distinction: Native Mode process vs. Compatibility Mode process ...
but people pointed out, quite correctly, that a process might want
to switch from NM to CM to NM ... so a process is just a process ... the
NM/CM mode is no longer a type of process.)
What does the MPE example have to do with Linux? Everything...what happens
when your "linux process" wants to dynamically load code from an HP-UX
library? Or vice versa? What about shared libraries?
Take it from someone who's been there: having a "process type" isn't
a 100% solution. Having non-overlapping system call mechanism (either
different numbers or a different address) provides a much closer to
100% solution. You may still need to translate things to provide
data back to an HP-UX system call (e.g., process structure for pstat?),
but that's *doable* ... and the translator method won't get that far!
--
Stan Sieler sieler@allegro.com
http://www.allegro.com/sieler/
next prev parent reply other threads:[~1999-06-21 20:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-21 18:20 [parisc-linux] HPUX binary compatibility Mike Hibler
1999-06-21 20:49 ` Stan Sieler [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-06-20 17:40 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 17:23 ` 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
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=199906212049.NAA32096@bart.allegro.com \
--to=sieler@allegro.com \
--cc=mike@fast.cs.utah.edu \
--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