From: "Måns Rullgård" <mans@mansr.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matt Turner <mattst88@gmail.com>, Borislav Petkov <bp@alien8.de>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Matthew Wilcox <willy@infradead.org>,
Jann Horn <jannh@google.com>, Al Viro <viro@zeniv.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
kernel list <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
linux-alpha <linux-alpha@vger.kernel.org>,
linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH] x86: Deprecate a.out support
Date: Mon, 11 Mar 2019 19:47:25 +0000 [thread overview]
Message-ID: <yw1x1s3d42ia.fsf@mansr.com> (raw)
In-Reply-To: <CAHk-=wiU7xacTqDfm-x29-meyJWNd_X95K0T8FQMcDgy-yo3Qw@mail.gmail.com> (Linus Torvalds's message of "Mon, 11 Mar 2019 12:03:18 -0700")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Mon, Mar 11, 2019 at 11:08 AM Måns Rullgård <mans@mansr.com> wrote:
>>
>> The latest version I have is 5.1, and that uses ECOFF.
>
> ECOFF _is_ a.out as far as Linux is concerned.
>
> So Linux basically treats ECOFF as "regular a.out with just some
> header extensions".
>
> We don't have any specific support for ECOFF.
>
> I _think_. Again, it's been years and years.
Right, which is why killing a.out entirely would have the unfortunate
effect of also removing the OSF/1 compatibility on Alpha.
If we are to support Alpha as an architecture at all, it makes sense to
support the things people actually use it for.
Now, personally I can live without it. I just don't like to see
features removed without due consideration.
--
Måns Rullgård
WARNING: multiple messages have this Message-ID (diff)
From: "Måns Rullgård" <mans@mansr.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matt Turner <mattst88@gmail.com>, Borislav Petkov <bp@alien8.de>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Matthew Wilcox <willy@infradead.org>,
Jann Horn <jannh@google.com>, Al Viro <viro@zeniv.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
kernel list <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"the arch\/x86 maintainers" <x86@kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
linux-alpha <linux-alpha@vger.kernel.org>,
linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH] x86: Deprecate a.out support
Date: Mon, 11 Mar 2019 19:47:25 +0000 [thread overview]
Message-ID: <yw1x1s3d42ia.fsf@mansr.com> (raw)
In-Reply-To: <CAHk-=wiU7xacTqDfm-x29-meyJWNd_X95K0T8FQMcDgy-yo3Qw@mail.gmail.com> (Linus Torvalds's message of "Mon, 11 Mar 2019 12:03:18 -0700")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Mon, Mar 11, 2019 at 11:08 AM Måns Rullgård <mans@mansr.com> wrote:
>>
>> The latest version I have is 5.1, and that uses ECOFF.
>
> ECOFF _is_ a.out as far as Linux is concerned.
>
> So Linux basically treats ECOFF as "regular a.out with just some
> header extensions".
>
> We don't have any specific support for ECOFF.
>
> I _think_. Again, it's been years and years.
Right, which is why killing a.out entirely would have the unfortunate
effect of also removing the OSF/1 compatibility on Alpha.
If we are to support Alpha as an architecture at all, it makes sense to
support the things people actually use it for.
Now, personally I can live without it. I just don't like to see
features removed without due consideration.
--
Måns Rullgård
next prev parent reply other threads:[~2019-03-11 19:47 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 23:57 a.out coredumping: fix or delete? Jann Horn
2019-03-03 1:09 ` Andy Lutomirski
2019-03-05 9:19 ` Borislav Petkov
2019-03-05 12:22 ` Matthew Wilcox
2019-03-05 13:43 ` Alan Cox
2019-03-05 14:59 ` [PATCH] x86: Deprecate a.out support Borislav Petkov
2019-03-05 15:17 ` Richard Weinberger
2019-03-05 16:22 ` Linus Torvalds
2019-03-05 16:30 ` Jann Horn
2019-03-05 17:32 ` Borislav Petkov
2019-03-05 17:31 ` Borislav Petkov
2019-03-05 17:58 ` Linus Torvalds
2019-03-05 18:11 ` Borislav Petkov
2019-03-05 18:18 ` Borislav Petkov
2019-03-06 15:07 ` Geert Uytterhoeven
2019-03-10 21:37 ` Matt Turner
2019-03-10 22:40 ` Linus Torvalds
2019-03-10 23:19 ` Al Viro
2019-03-11 7:20 ` John Paul Adrian Glaubitz
2019-03-11 11:02 ` Arnd Bergmann
2019-03-11 16:26 ` Måns Rullgård
2019-03-11 16:26 ` Måns Rullgård
2019-03-11 16:45 ` Linus Torvalds
2019-03-11 18:08 ` Måns Rullgård
2019-03-11 18:08 ` Måns Rullgård
2019-03-11 19:03 ` Linus Torvalds
2019-03-11 19:47 ` Måns Rullgård [this message]
2019-03-11 19:47 ` Måns Rullgård
2019-03-11 20:50 ` Matt Turner
2019-03-11 20:50 ` Matt Turner
2019-03-11 21:34 ` Arnd Bergmann
2019-03-11 21:34 ` Arnd Bergmann
2019-03-11 21:45 ` Linus Torvalds
2019-03-11 22:12 ` Måns Rullgård
2019-03-11 22:12 ` Måns Rullgård
2019-03-12 8:44 ` Geert Uytterhoeven
2019-03-14 18:38 ` Miguel Ojeda
2019-03-14 18:38 ` Miguel Ojeda
2019-03-11 22:06 ` Måns Rullgård
2019-03-11 22:06 ` Måns Rullgård
2019-03-11 22:11 ` Matt Turner
2019-03-12 6:38 ` Michael Cree
2019-04-16 3:19 ` Jon Masters
2019-03-11 18:58 ` Matt Turner
2019-03-06 16:55 ` Enrico Weigelt, metux IT consult
2019-03-06 17:52 ` [PATCH] fs: binfmt: mark aout as broken Enrico Weigelt, metux IT consult
2019-03-06 12:25 ` a.out coredumping: fix or delete? Thomas Gleixner
2019-03-06 14:11 ` Theodore Y. Ts'o
2019-03-06 14:11 ` Theodore Y. Ts'o
2019-03-06 16:52 ` Alan Cox
2019-03-06 16:52 ` Alan Cox
2019-03-06 17:45 ` Andy Lutomirski
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=yw1x1s3d42ia.fsf@mansr.com \
--to=mans@mansr.com \
--cc=akpm@linux-foundation.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=bp@alien8.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=jannh@google.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=mattst88@gmail.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.