From: Al Viro <viro@ZenIV.linux.org.uk>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: what's parisc execve_wrapper doing in the end?
Date: Thu, 4 Oct 2012 15:07:59 +0100 [thread overview]
Message-ID: <20121004140759.GK23473@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAE2sS1jrFOgwt3xRsnDv5uQ7kYx16vy+nEeK5oGpD3Yd-7fVfQ@mail.gmail.com>
On Thu, Oct 04, 2012 at 09:30:16AM -0400, Carlos O'Donell wrote:
> On Thu, Oct 4, 2012 at 8:57 AM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >> Unless I'm missing something really subtle, it looks like HPUX compat had
> >> been very noticably broken since at least 2002. Comments?
> >
> > I think it probably has. I don't believe there's anyone left with hpux
> > binaries actually checking it.
>
> Was the HPUX support ever completed?
>
> I had HPUX/Linux dual-boot on one of my systems and I was never able
> to run an HPUX binary correctly.
>
> Someone with the time and inclination is all that is missing to
> cleanup the rotten HPUX bits.
>
> There is no need to keep any of it around, that's what version control is for.
FWIW, parisc seems to be the last architecture to keep such thing - sparc
and mips had dropped SunOS/Solaris/IRIX compat, iBCS* is long-dead (and hadn't
been in mainline kernel anyway). Alpha might still be able to run some OSF
binaries, but there the situation is different - no alternative syscall
entry codepath, Linux just uses the same ABI and shares syscall numbers
where possible...
next prev parent reply other threads:[~2012-10-04 14:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121004045150.GH23473@ZenIV.linux.org.uk>
2012-10-04 9:30 ` what's parisc execve_wrapper doing in the end? James Bottomley
2012-10-05 11:07 ` James Bottomley
2012-10-05 13:44 ` James Bottomley
2012-10-05 14:47 ` James Bottomley
2012-10-05 14:48 ` Al Viro
2012-10-05 14:55 ` James Bottomley
2012-10-05 19:21 ` Al Viro
2012-10-05 23:04 ` Al Viro
2012-10-08 11:28 ` James Bottomley
2012-10-09 9:55 ` James Bottomley
2012-10-10 4:26 ` Al Viro
2012-10-05 22:54 ` John David Anglin
2012-10-05 23:32 ` Al Viro
2012-10-06 0:15 ` John David Anglin
[not found] ` <20121004051359.GA24664@ZenIV.linux.org.uk>
2012-10-04 10:02 ` James Bottomley
2012-10-04 12:22 ` Al Viro
2012-10-04 12:57 ` James Bottomley
2012-10-04 13:30 ` Carlos O'Donell
2012-10-04 14:07 ` Al Viro [this message]
2012-10-05 0:00 ` John David Anglin
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=20121004140759.GK23473@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=James.Bottomley@hansenpartnership.com \
--cc=carlos@systemhalted.org \
--cc=linux-parisc@vger.kernel.org \
/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.