From: willy@thepuffingroup.com
To: "MEYER,ALAN C. HP-FtCollins,ex1\"" <alan_meyer@hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] HP-UX application support?
Date: Mon, 28 Feb 2000 17:04:46 -0500 [thread overview]
Message-ID: <20000228170446.Z9944@thepuffingroup.com> (raw)
In-Reply-To: <56D553C0B61BD311AD2300A0C9F485C2038D0FD0@xfc02.fc.hp.com>; from MEYER,ALAN C. HP-FtCollins,ex1" on Mon, Feb 28, 2000 at 02:14:17PM -0700
On Mon, Feb 28, 2000 at 02:14:17PM -0700, MEYER,ALAN C. HP-FtCollins,ex1" wrote:
> I have heard several descriptions of what will be supported for HP-UX
> applications on 64-bit PA/Linux.
>
> Can someone plz clarify what will be supported:
> * 64-bit/ELF HP-UX applications
> * 32-bit/SOM HP-UX applications
We intend to support both of the above; in addition we also intend to
support 32 bit ELF Linux applications and, eventually, 64 bit ELF Linux
applications. In case anyone didn't realise it, the current executables
we use are 32-bit SOM HP-UX applications. Admittedly, the current sash
we have implements `-mount' by calling a linux syscall, but that's only
one command.
Not every application will work, but the vast majority of them will.
Binary support for threaded applications is most unlikely.
> And, what about the install location of HP-UX shlibs required for these
> 64-bit (and 32-bit?) HP-UX applications?
If we use a dynamically linked application, they would need to be placed
in the same location that HP/UX requires them to be.
> Also, I am assuming the install model will be to simply copy files from an
> HP-UX system over to a PA/Linux system. In particular, I have heard of no
> plans to support HP-UX packages bundled in "SD" format. Right?
Hmmm.. this is really a userspace problem that we haven't thought
about yet. I anticipate that the `swinstall' program will work without
much pain and therefore installing .depot files will work. However,
it wouldn't be the recommended way; packaging products as rpm or dpkg
(depending which distribution we pick) would be the preferred way to go.
There is a program called `alien' which can install other package formats,
extending that to support .depot files might be a fun thing to do for
someone with too much time on their hands :-)
next prev parent reply other threads:[~2000-02-28 23:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-28 21:14 [parisc-linux] HP-UX application support? MEYER,ALAN C. (HP-FtCollins,ex1)
2000-02-28 22:04 ` willy [this message]
2000-02-28 22:26 ` Philipp Rumpf
2000-02-28 22:55 ` Grant Grundler
2000-02-28 23:26 ` willy
2000-03-12 2:36 ` Steven Pritchard
2000-03-13 9:02 ` Corne Beerse
-- strict thread matches above, loose matches on Subject: below --
2000-02-28 22:47 FINK,MARTIN (HP-FtCollins,ex1)
2000-02-28 23:04 ` willy
2000-02-29 0:08 MEYER,ALAN C. (HP-FtCollins,ex1)
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=20000228170446.Z9944@thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=alan_meyer@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox