public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: NULL <ayz.out@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	x86@kernel.org, arnd@arndb.de, Kees Cook <keescook@chromium.org>
Subject: Re: Request: Regarding the phasing out of "a.out support" in Linux Kernels
Date: Sun, 10 Apr 2022 00:55:44 +0200	[thread overview]
Message-ID: <YlIO8GbSYN9xANnb@zn.tnic> (raw)
In-Reply-To: <CADt9uBnKs9p5BP6qF8+v+gQ8Pe7S10_CSiFLAr9GyBWnftGqUQ@mail.gmail.com>

[ Readding back previous recipients. ]

On Sat, Apr 09, 2022 at 05:16:52PM +0100, NULL wrote:
> Thank you for your reply, I was hoping more that the 327 aout.o lines would
> remain in makefile & arch /ia32/ia32_aout.c for 5.19 (even if ignored by
> default KConfig flags as a test to see if it would break anything for
> other) as opposed to the currently proposed PR.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/diff/?h=x86/cleanups&id=f9444ea5e20847d1dd4a98d4dff4cc97655834bb
> 
>  Essentially just asking for 5.19 to announce the proposed removal & to
> hold/push the ia32 commits back by one or two releases, With complete
> removal of all the code only occurring in 5.21's Release.

First of all, please hit "reply-to-all" when replying to a mail on a
public mailing list so that others can see the conversation too and can
participate, if they wish.

Then, it is kinda hard to take you seriously if your name is "NULL" or
"Non Null". If I'm using my real name - you could too.

Furthermore, you haven't given any concrete reason why you'd need this
except maybe something along the lines that it might be good to have it
in an LTS release. And that's not nearly a good reason to keep ancient
code which no one uses and which current toolchains can't even produce.

If you've followed the previous discussions, there was a pretty simple
ELF loader posted for a.out executables so it's not like there are no
alternatives. You can also run an older kernel in a VM. And so on...

Finally, pls do not top-post but put your reply underneath the next
you're commenting on like I just did.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  parent reply	other threads:[~2022-04-09 22:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADt9uBkMkrywjSo_jyUJtS85ATTQtRTVXPRsRVUKZpujYo9SUQ@mail.gmail.com>
2022-04-09 15:37 ` Request: Regarding the phasing out of "a.out support" in Linux Kernels Borislav Petkov
     [not found]   ` <CADt9uBnKs9p5BP6qF8+v+gQ8Pe7S10_CSiFLAr9GyBWnftGqUQ@mail.gmail.com>
2022-04-09 22:55     ` Borislav Petkov [this message]
     [not found] ` <CADt9uBmCpGDOgd24QA=5sbO+JVQMA+z8xTO5z3W=MWyM9hsiSw@mail.gmail.com>
     [not found]   ` <CADt9uB=OwN2OtzDfOk+SjF2QWdZnyzmD6KeqNd-gxZ_j6dkW4g@mail.gmail.com>
     [not found]     ` <CADt9uBk+s04NFr+MepmqdLEbbt4d7tmZ5Jxz2jV8v6SmkdnaAA@mail.gmail.com>
2022-04-09 15:38       ` Fwd: " NULL

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=YlIO8GbSYN9xANnb@zn.tnic \
    --to=bp@alien8.de \
    --cc=arnd@arndb.de \
    --cc=ayz.out@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox