From: Eric W. Biederman <hidden> Date: 2020-05-19 12:00:32
Andreas Schwab [off-list ref] writes:
On Mai 18 2020, Eric W. Biederman wrote:
quoted
If it was only libc4 and libc5 that used the uselib system call then it
can probably be removed after enough time.
Only libc4 used it, libc5 was already ELF.
binfmt_elf.c supports uselib. In a very a.out ish way. Do you know if
that support was ever used?
If we are truly talking a.out only we should be able to make uselib
conditional on a.out support in the kernel which is strongly mostly
disabled at this point.
I am wondering if there are source trees for libc4 or libc5 around
anywhere that we can look at to see how usage of uselib evolved.
Eric
From: Christian Brauner <hidden> Date: 2020-05-19 13:14:07
On Tue, May 19, 2020 at 06:56:36AM -0500, Eric W. Biederman wrote:
Andreas Schwab [off-list ref] writes:
quoted
On Mai 18 2020, Eric W. Biederman wrote:
quoted
If it was only libc4 and libc5 that used the uselib system call then it
can probably be removed after enough time.
Only libc4 used it, libc5 was already ELF.
binfmt_elf.c supports uselib. In a very a.out ish way. Do you know if
that support was ever used?
If we are truly talking a.out only we should be able to make uselib
conditional on a.out support in the kernel which is strongly mostly
disabled at this point.
Hi Christian,
On Tue, May 19, 2020 at 3:15 PM Christian Brauner
[off-list ref] wrote:
On Tue, May 19, 2020 at 06:56:36AM -0500, Eric W. Biederman wrote:
quoted
Andreas Schwab [off-list ref] writes:
quoted
On Mai 18 2020, Eric W. Biederman wrote:
quoted
If it was only libc4 and libc5 that used the uselib system call then it
can probably be removed after enough time.
Only libc4 used it, libc5 was already ELF.
binfmt_elf.c supports uselib. In a very a.out ish way. Do you know if
that support was ever used?
If we are truly talking a.out only we should be able to make uselib
conditional on a.out support in the kernel which is strongly mostly
disabled at this point.
Quoting myself (for the second time this month):
"I think it's safe to assume no one still runs a.out binaries on m68k."
http://lore.kernel.org/r/CAMuHMdW+m0Q+j3rsQdMXnrEPm+XB5Y2AQrxW5sD1mZAKgmEqoA@mail.gmail.com
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
From: Christian Brauner <hidden> Date: 2020-05-19 14:47:50
On Tue, May 19, 2020 at 04:32:38PM +0200, Geert Uytterhoeven wrote:
Hi Christian,
On Tue, May 19, 2020 at 3:15 PM Christian Brauner
[off-list ref] wrote:
quoted
On Tue, May 19, 2020 at 06:56:36AM -0500, Eric W. Biederman wrote:
quoted
Andreas Schwab [off-list ref] writes:
quoted
On Mai 18 2020, Eric W. Biederman wrote:
quoted
If it was only libc4 and libc5 that used the uselib system call then it
can probably be removed after enough time.
Only libc4 used it, libc5 was already ELF.
binfmt_elf.c supports uselib. In a very a.out ish way. Do you know if
that support was ever used?
If we are truly talking a.out only we should be able to make uselib
conditional on a.out support in the kernel which is strongly mostly
disabled at this point.
Well, it's just a great thing to hear. :)
Fyi, I once tried to give a demo with a Slackware version in a container
which pre-dated ELF on a x86 kernel with AOUT. It didn't go well...
Christian