From: Andi Kleen <ak@suse.de>
To: Theodore Tso <tytso@mit.edu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Deprecate a.out ELF interpreters
Date: Thu, 2 Aug 2007 00:59:25 +0200 [thread overview]
Message-ID: <200708020059.25383.ak@suse.de> (raw)
In-Reply-To: 20070801221448.GF28106@thunk.org
On Thursday 02 August 2007 00:14:48 Theodore Tso wrote:
> Do you mean deprecate a.out interpreters?
No, just a.out interpreters for ELF binaries.
> I could imagine that there might be some people running some very old
> statically linked programs from a decade or so ago, but I agree they
> are pretty small in number.
Nothing would change for them.
The only thing that would change is that if someone has a a.out system
with ELF executables then they would need to update their ELF ld.so to ELF.
Dynamically linked a.out executables should also still run because they
use a different ld.so.
> Is the fs/binfmt_aout.c causing problems?
> It's only 562 lines of code...
I'm not concerned about binfmt_aout; just about the special case a.out ld.so
code in binfmt_elf.
-Andi
prev parent reply other threads:[~2007-08-01 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 12:31 [RFC] Deprecate a.out ELF interpreters Andi Kleen
2007-08-01 22:14 ` Theodore Tso
2007-08-01 22:59 ` Andi Kleen [this message]
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=200708020059.25383.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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