[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whD1SumZUBQeuMT-GcciwPxg_jW_TsPAmokYp3sGGCGhA@mail.gmail.com>
Date: Mon, 11 Mar 2019 09:45:32 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Måns Rullgård <mans@...sr.com>
Cc: Matt Turner <mattst88@...il.com>, Borislav Petkov <bp@...en8.de>,
Alan Cox <gnomes@...rguk.ukuu.org.uk>,
Matthew Wilcox <willy@...radead.org>,
Jann Horn <jannh@...gle.com>,
Al Viro <viro@...iv.linux.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
kernel list <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
Linux API <linux-api@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Richard Weinberger <richard@....at>,
Anton Ivanov <anton.ivanov@...bridgegreys.com>,
linux-alpha <linux-alpha@...r.kernel.org>,
linux-m68k@...ts.linux-m68k.org
Subject: Re: [PATCH] x86: Deprecate a.out support
On Mon, Mar 11, 2019 at 9:26 AM Måns Rullgård <mans@...sr.com> wrote:
>
> Anyone running an Alpha machine likely also has some old OSF/1 binaries
> they may wish to use. It would be a shame to remove this feature, IMO.
If that's the case then we'd have to keep a.out alive for alpha, since
that's the OSF/1 binary format (at least the only one we support - I'm
not sure if later versions of OSF/1 ended up getting ELF).
Which I guess we could do, but the question is whether people really
do have OSF/1 binaries. It was really useful early on as a source of
known-good binaries to test with, but I'm not convinced it's still in
use.
It's not like there were OSF/1 binaries that we didn't havce access to
natively (well, there _were_ special ones that didn't have open source
versions, but most of them required more system-side support than
Linux ever implemented, afaik).
Linus
Powered by blists - more mailing lists