From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <ak@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] Deprecate a.out ELF interpreters
Date: Wed, 01 Aug 2007 11:02:25 -0400 [thread overview]
Message-ID: <46B0A081.5080405@zytor.com> (raw)
In-Reply-To: <200708011433.09433.ak@novell.com>
Andi Kleen wrote:
>
> I propose to deprecate this support and remove for 2.6.25.
>
> Drawback is that someone still runs their system with a.out ld.so
> they would need to update the ld.so when updating to a new kernel.
>
> This patch just adds an entry to the deprecation file and a printk
> warning users.
>
> Comments?
>
Makes total sense. This is a highly oddball configuration, and
*extremely* unlikely to have a significant user base of modern kernels.
It's been 12 years since we switched to ELF.
-hpa
next prev parent reply other threads:[~2007-08-01 15:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 12:33 [RFC] [PATCH] Deprecate a.out ELF interpreters Andi Kleen
2007-08-01 15:02 ` H. Peter Anvin [this message]
2007-08-01 18:30 ` Jan Engelhardt
2007-08-01 18:35 ` Andi Kleen
2007-08-01 19:26 ` Jan Engelhardt
2007-08-01 20:02 ` Christoph Hellwig
2007-08-01 20:13 ` Andi Kleen
2007-08-01 20:42 ` Jiri Kosina
2007-08-01 21:18 ` Rene Herman
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=46B0A081.5080405@zytor.com \
--to=hpa@zytor.com \
--cc=ak@novell.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox