From: Andi Kleen <andi@firstfloor.org>
To: David Newall <davidn@davidnewall.com>
Cc: Andi Kleen <andi@firstfloor.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for mm] Remove iBCS support
Date: Sun, 20 Jan 2008 04:11:53 +0100 [thread overview]
Message-ID: <20080120031153.GB6275@one.firstfloor.org> (raw)
In-Reply-To: <4792B191.2060801@davidnewall.com>
On Sun, Jan 20, 2008 at 12:57:29PM +1030, David Newall wrote:
> Andi Kleen wrote:
> > Can you please queue this patch in -mm for .25. It was posted earlier
> > and nobody complained.
>
> I'm sure I complained. I'm sure I said something about SCO
Did you?
> compatibility. This is a sleeping giant for Linux. There are plenty of
Interesting choice of words.
> machines running legacy SCO applications, just waiting for painless
> migration to some other platform.
>
> We should not be dismantling the scaffolding that's needed for that.
See the rationale in the patch -- any iBCS application will need a significant
kernel patch. If people add this kernel patch they can easily patch the three
more places that detect the executables.
But it does not make sense for all Linux kernels to always check for iBCS executables
when they don't have to code to run them anyways.
Now if iBCS support is truly as important as you claim I'm sure
someone will eventually submit a patch for mainline to support it properly.
If yes the hooks can be readded in a clean way, not in a hackish way
like they currently exists.
-Andi
>
next prev parent reply other threads:[~2008-01-20 3:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 4:59 [PATCH for mm] Remove iBCS support Andi Kleen
2008-01-20 2:27 ` David Newall
2008-01-20 3:11 ` Andi Kleen [this message]
2008-01-20 4:46 ` David Newall
2008-01-20 5:18 ` Andi Kleen
2008-01-20 5:33 ` David Newall
2008-01-20 5:55 ` Andi Kleen
2008-01-20 6:23 ` David Newall
2008-01-20 7:29 ` Andi Kleen
2008-01-21 1:37 ` David Newall
2008-01-22 10:24 ` Karl Kiniger
2008-01-22 15:06 ` David Newall
2008-01-22 15:52 ` Adrian Bunk
2008-01-23 8:48 ` Andi Kleen
2008-01-23 14:12 ` Karl Kiniger
2008-01-23 14:24 ` Andi Kleen
2008-01-24 17:06 ` David Newall
2008-01-22 11:12 ` Ingo Molnar
2008-01-22 12:42 ` Karl Kiniger
2008-01-22 15:13 ` David Newall
2008-01-22 15:49 ` Ingo Molnar
2008-01-24 17:01 ` David Newall
2008-01-22 16:01 ` Adrian Bunk
2008-01-24 17:04 ` David Newall
2008-01-24 17:24 ` Adrian Bunk
2008-01-24 17:55 ` David Newall
2008-01-24 18:14 ` Adrian Bunk
2008-01-25 2:14 ` David Newall
2008-01-25 5:12 ` Valdis.Kletnieks
2008-01-25 16:40 ` Alan Cox
2008-01-24 19:51 ` Pavel Machek
2008-01-25 2:17 ` David Newall
2008-01-24 20:37 ` Andi Kleen
2008-01-25 2:16 ` David Newall
2008-01-22 16:50 ` Alan Cox
2008-01-24 17:08 ` David Newall
2008-01-22 13:20 ` Giulio
2008-01-20 13:06 ` Alan Cox
2008-01-20 13:43 ` David Newall
2008-01-20 13:51 ` Alan Cox
2008-01-25 12:17 ` Ingo Molnar
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=20080120031153.GB6275@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@osdl.org \
--cc=davidn@davidnewall.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