From: Borislav Petkov <bp@alien8.de>
To: Theodore Ts'o <tytso@mit.edu>
Cc: X86 ML <x86@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Remove a.out support
Date: Fri, 14 Jan 2022 20:09:21 +0100 [thread overview]
Message-ID: <YeHKYXssmfX9Lfrr@zn.tnic> (raw)
In-Reply-To: <YeD2q77KmaD8k87Q@mit.edu>
Just to answer the "do we still wanna support running original a.out
binaries" aspect...
On Thu, Jan 13, 2022 at 11:06:03PM -0500, Theodore Ts'o wrote:
> > > Let's pour one out for being able to run Minix binaries on Linux. :-)
> >
> > https://en.wikipedia.org/wiki/Minix_3:
> >
> > "2013-02-21 ... Dropped support for a.out binaries"
> >
> > They themselves killed that support a lot earlier. :-)
>
> Well, Minix 3 is a very different beast than the Minix 1.x
Right, but if the Minix 1.x successor has deemed a.out support obsolete
and has removed in 2013 I figure we can too. :-)
And, btw, Alan had a good, practical idea at the time we talked about
deprecating a.out support:
https://lore.kernel.org/all/20190305134347.4be2449c@alans-desktop/
And that is probably the best thing to do: if people wanna run old a.out
binaries, they can either write an a.out loader as an ELF program or
slap an old linux distro in a VM and do that there just fine.
If you look at the original thread which started this:
https://lore.kernel.org/all/CAG48ez1RVd5mQ_Pb6eygQESaZhpQz765OAZYSoPE0kPqfZEXQg@mail.gmail.com/
it looked even back then like a.out support is so rusty, bitrotten and
broken that we're probably even doing ourselves a favor to remove it.
Especially if not even the toolchains would even create an a.out
executable and no one even noticed.
So...
> that Linus used when he was boot-strapping Linux back in 1991. :-)
>
> Among other things Minux 1.x is system call compatible with the
> original V7 Unix from AT&T, whereas Minux 2.x and higher switch to
> having system calls that were Posix comaptible --- and Minix 2, being
> at teaching OS, wouldn't have kept any backwards compatibility when
> Prof. Tannenbaum released the 2nd edition of his Operating Systems
> Design and Implementation book in 1997.
I had a lot of fun reading that book. :-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-01-14 19:09 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 16:01 [PATCH] x86: Remove a.out support Borislav Petkov
2022-01-13 18:08 ` Kees Cook
2022-01-13 18:47 ` Theodore Ts'o
2022-01-13 22:56 ` Borislav Petkov
2022-01-14 4:06 ` Theodore Ts'o
2022-01-14 10:40 ` Arnd Bergmann
2022-01-14 19:09 ` Borislav Petkov [this message]
2022-01-14 9:51 ` David Laight
2022-01-14 14:52 ` Geert Uytterhoeven
2022-01-14 18:57 ` Theodore Ts'o
2022-01-14 19:00 ` Geert Uytterhoeven
2022-01-14 19:12 ` Borislav Petkov
2022-01-14 19:21 ` Geert Uytterhoeven
2022-01-14 19:35 ` Borislav Petkov
2022-01-15 11:37 ` Borislav Petkov
2022-01-15 19:42 ` John Paul Adrian Glaubitz
2022-03-09 20:03 ` [PATCH] a.out: Stop building a.out/osf1 support on alpha and m68k Eric W. Biederman
2022-03-09 20:37 ` Linus Torvalds
2022-03-09 22:02 ` Kees Cook
2022-03-09 22:04 ` Kees Cook
2022-03-10 23:29 ` [PATCH] x86: Remove a.out support Eric W. Biederman
2022-03-10 23:35 ` Linus Torvalds
2022-03-11 8:47 ` Arnd Bergmann
2022-03-11 10:03 ` Borislav Petkov
2022-03-10 8:09 ` [PATCH] a.out: Stop building a.out/osf1 support on alpha and m68k Geert Uytterhoeven
2022-01-15 4:54 ` [PATCH] x86: Remove a.out support David Laight
2022-03-11 14:40 ` [tip: x86/cleanups] " tip-bot2 for Borislav Petkov
2022-04-11 17:42 ` tip-bot2 for Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2022-03-12 17:54 [PATCH] " James Jones
2022-03-12 18:06 ` James Jones
2022-03-13 11:56 ` Borislav Petkov
2022-03-13 18:26 ` James Jones
2022-03-15 9:44 ` Borislav Petkov
2022-03-15 19:51 ` Kees Cook
2022-03-16 5:06 ` James Jones
2022-03-16 12:38 ` Arnd Bergmann
2022-03-16 22:30 ` Kees Cook
2022-03-17 2:04 ` James Jones
2022-03-17 2:08 ` David Laight
2022-03-17 10:17 ` Borislav Petkov
2022-03-17 18:53 ` Kees Cook
2022-03-17 2:32 ` David Laight
2022-03-17 3:22 ` Kees Cook
2022-03-16 16:10 ` Kees Cook
2022-03-16 17:05 ` David Laight
2022-04-02 22:14 ` Maciej W. Rozycki
2022-04-03 2:24 ` Kees Cook
2022-04-04 11:03 ` Maciej W. Rozycki
2022-04-04 17:07 ` David Laight
2022-04-04 18:18 ` Kees Cook
2022-04-04 8:24 ` Geert Uytterhoeven
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=YeHKYXssmfX9Lfrr@zn.tnic \
--to=bp@alien8.de \
--cc=arnd@arndb.de \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--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