[Relocatable binaries - better kernel support?] On 03/11/2022 (Thu 13:56)
Richard Purdie wrote:
[...]
> The code that handles the interpreter is in the kernel, in
> fs/binfmt_elf.c:load_elf_binary(). The idea would be to add support for
> $ORIGIN there so that $ORIGIN is replaced with the
On Thu, 2022-11-03 at 10:20 -0400, Paul Gortmaker wrote:
> [Relocatable binaries - better kernel support?] On 03/11/2022 (Thu 13:56)
> Richard Purdie wrote:
>
> [...]
>
> > The code that handles the interpreter is in the kernel, in
> > fs/binfmt_elf.c:load_elf_binary(). The idea would be to add
On Thu, 2022-11-03 at 15:24 +0100, Alexander Kanavin wrote:
> On Thu, 3 Nov 2022 at 14:56, Richard Purdie
> wrote:
>
> > The code that handles the interpreter is in the kernel, in
> > fs/binfmt_elf.c:load_elf_binary(). The idea would be to add support for
> > $ORIGIN there so that $ORIGIN is
On Thu, 3 Nov 2022 at 14:56, Richard Purdie
wrote:
> The code that handles the interpreter is in the kernel, in
> fs/binfmt_elf.c:load_elf_binary(). The idea would be to add support for
> $ORIGIN there so that $ORIGIN is replaced with the location of the
> binary.
>
> Does anyone have an idea if
I thought I'd quickly write down some notes on the relocatable binary
"problem" we have.
We have a need to be able to run our binaries with a different dynamic
loader in a few cases which basically come down to:
* uninative relocation of "native" binaries so they work on differentÂ
distros via
