[LWN subscriber-only content]
Welcome to LWN.salvage
The next subscription-simplest vow has been made on hand to you
by an LWN subscriber. Thousands of subscribers rely upon LWN for the
finest news from the Linux and free draw communities. Have to you pick up pleasure from this
article, please maintain in thoughts subscribing to LWN. Thank you
for visiting LWN.salvage!
By Jonathan Corbet
March 24, 2022
The a.out executable
structure dates attend to the earliest days of Linux — and sooner than. It has
no longer been feeble in any serious technique for a long time, but toughen calm exists in
the Linux kernel and has resisted all makes an attempt at its removal. Inspire in
January, Borislav Petkov tried yet
all all over again to delete toughen for this structure, ensuing in one other extended
dialogue. There’s one difference this time spherical, even supposing: the effort
to set apart away with a.out toughen can also lawful be triumphant.
The a.out structure dates attend to the principle edition of Unix. When MINIX got right here
alongside, it naturally feeble that structure for its executable recordsdata; that, in
turn, led to a.out being feeble in Linux as effectively. It’s miles a easy structure, and
its implementation on Linux used to be even more purposeful; amongst different issues, every
Linux shared library wanted to be centrally assigned its maintain piece of the
contend with utter, since libraries can also no longer be relocated at bustle time. Unruffled, Linux
feeble a.out for some time, unless toughen for the newfangled ELF structure used to be
first added to the 0.99.13 trend kernel in 1993.
There used to be a time when the crazier folk amongst us manually converted our
Slackware programs from a.out to ELF in advise in an effort to ascertain out it out and
originate the advantages sooner than distributions were up up to now. They calm maintain the
scars from that time. Not that your editor
would ever admit to shimmering any individual who would fill engaged in any such process.
ELF has been the bizarre executable structure for Linux on most architectures
since 1995. One can also mediate that would possibly well perchance perchance fill equipped ample time for any
customers of a.out binaries to grudgingly cross on to ELF; its adoption can
doubtlessly be judged to no longer be a passing fad at this level. But, in the
real world, surprises lurk.
The initial dialog on eradicating a.out feeble out rather immediate, but
used to be restarted when Eric Biederman posted
a patch disabling the building of a.out toughen on the 2
architectures (Alpha and m68k) that also allow it by default. This patch
did no longer in actuality purchase away the toughen, it lawful changed into it off to search if
any individual would bellow. If protests were raised, toughen would be changed into
attend on immediate and with out problems; otherwise a beefy removal would be performed.
Linus Torvalds immediate answered
that he used to be “rather distinct we can not pause this“. He pointed out
that the native executable structure on Alpha programs running Digital’s Unix
used to be in actuality a.out, even though it went by the more moderen name of ECOFF. The
Linux a.out loader can bustle ECOFF programs by advantage of ignoring among the
more moderen ECOFF parts; taking it out would damage any programs calm utilizing
that toughen. One can also mediate that the assortment of customers who’re calm utilizing
Alpha CPUs, running ECOFF binaries on these CPUs, and monitoring contemporary
kernel releases can also simply be a rather small quantity, but one never knows.
Kees Cook did pause
a little bit evaluate on, apparently, the finest distribution that also
helps Alpha (Gentoo) and came at some level of that the finest ECOFF recordsdata contemporary
contained firmware, which does no longer bustle on the CPU anyway. He concluded
that there would be no damage from eradicating a.out toughen on this platform:
“Let’s pause it“.
It looks to be a traditional rule that somebody consistently has to near attend alongside to
destroy the occasion. In this case, lawful as it seemed esteem there were no extra
boundaries to the removal of a.out, James Jones showed
up to let it be identified that he used to be calm utilizing a.out:
The inform case is running an used spot of tools to set apart programs for
the Atari Jaguar. Particularly, Atari’s assembler (mac) and linker
(aln). The different is running windows versions in dosbox, or
utilizing some replacements that were developed in accordance with a honest trusty
older, less-featureful model of the source code for mac and aln,
but which calm haven’t managed to add attend in the total parts
wished to set apart some programs or inform the Atari debugging tools
(Also on hand in a.out simplest).
He gave some more small print on why he calm wished to inform these tools in this
followup message
Transferring a program to a brand contemporary executable structure is in overall lawful a matter of
rebuilding the program. But rebuilding is a grand more complicated process in
the absence of the source code. Discovering oneself caught trying to bustle a
a long time-used binary on novel programs is lawful in actual fact among the a gigantic assortment of joys reserved
for customers of proprietary draw — but many contributors fill came at some level of themselves
in that place at one time or one other. They are legit Linux customers,
and there is no longer any desire to rupture their programs. So Petkov duly gave up and asked
simplest that Jones doc his usage of a.out for the benefit of folk that
can also attempt to purchase away it in the long bustle.
Cook, however, used to be no longer so fleet to throw in the towel; he seemed on the
programs in quiz and concluded that
it’ll also simply be doable to write an ELF wrapper program that can also load and
bustle used a.out binaries. Within the future later, he posted the form of
program, noting that it’ll also bustle the aln program on the least a ways
ample for it to bitch about its issue-line arguments. Jones tried
it out and used to be glad with the outcomes:
Certain, works perfectly, thanks. I esteem the premise of utilizing this grand
better than getting emailed every time someone needs to delete the
a.out code all all over again. Non-public in thoughts my inform case withdrawn. I’ve already
pushed an exchange to my jaguar-sdk mission to inform this draw as a change.
So removal of a.out toughen is attend in the plans for
the 5.18 kernel. Per chance the effort will be triumphant this time, even supposing there
are calm no guarantees; there is known as a.out customers who’re unaware of the
coming apocalypse and haven’t yet made their objections identified. If these
customers are unable or unwilling to inform Cook’s wrapper utility, the excision
of a.out toughen can also simply, all over all all over again, want to be deferred to some future kernel
commence.
(Log in to post feedback)