From: Richard Henderson <rth@twiddle.net>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: "Måns Rullgård" <mru@users.sourceforge.net>,
jlnance@intrex.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-rc1 broke OSF binaries on alpha
Date: Tue, 2 Jul 2002 16:13:22 -0700 [thread overview]
Message-ID: <20020702161322.A7642@twiddle.net> (raw)
In-Reply-To: <20020702190544.A23788@jurassic.park.msu.ru>; from ink@jurassic.park.msu.ru on Tue, Jul 02, 2002 at 07:05:44PM +0400
On Tue, Jul 02, 2002 at 07:05:44PM +0400, Ivan Kokshaysky wrote:
> Unfortunately the libraries _officially_ available for linux are
> from v4. If HP would release something more up to date, the alpha
> iov_len hack would go away.
Do we have any way of recognizing v4 vs v5 binaries? I don't think
we do. I'd be willing to call any ECOFF binary an OSF binary, and
ignore the fact that Linux used them in the distant past.
The minimum correct solution is to add a PER_OSF4 to personality.h
and put an osf_readv and osf_writev that, if PER_OSF4, read and frob
the data into kernel buffers and pass that on to the regular syscalls.
r~
next prev parent reply other threads:[~2002-07-02 23:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-28 10:54 2.4.19-rc1 broke OSF binaries on alpha Ivan Kokshaysky
2002-06-28 20:31 ` Marcelo Tosatti
2002-06-29 2:28 ` Alan Cox
2002-06-29 23:50 ` Ivan Kokshaysky
2002-07-01 7:54 ` Kurt Garloff
2002-07-01 16:17 ` Jeff Garzik
2002-07-01 13:03 ` jlnance
2002-07-01 14:02 ` Ivan Kokshaysky
2002-07-01 19:40 ` Måns Rullgård
2002-07-02 15:05 ` Ivan Kokshaysky
2002-07-02 23:13 ` Richard Henderson [this message]
2002-07-03 0:31 ` Ivan Kokshaysky
2002-06-29 2:26 ` Alan Cox
2002-06-29 22:45 ` Ivan Kokshaysky
2002-07-02 20:56 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2002-06-29 4:39 Chris Adams
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=20020702161322.A7642@twiddle.net \
--to=rth@twiddle.net \
--cc=ink@jurassic.park.msu.ru \
--cc=jlnance@intrex.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@users.sourceforge.net \
/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