Hi Laurent!
On 5/12/22 18:22, Laurent Vivier wrote:
>> I guess it's related to the glibc issue then [1].
>
> You can try by mounting your chroot on a non ext4 partition. It works well
> with btrfs.
>
> Ext4 stores a hash in a field that is normally an index, so a 64bit (host
> kernel long) has
Le 12/05/2022 à 18:16, John Paul Adrian Glaubitz a écrit :
Hi!
Hi :)
On 5/12/22 18:10, Laurent Vivier wrote:
The flags are correct.
This can be tested with:
$ sudo chroot m68k-chroot sh -c 'echo $0'
sh
if the argument is not properly managed, you would have "/usr/bin/sh".
Hi!
On 5/12/22 18:10, Laurent Vivier wrote:
> The flags are correct.
>
> This can be tested with:
>
> $ sudo chroot m68k-chroot sh -c 'echo $0'
> sh
>
> if the argument is not properly managed, you would have "/usr/bin/sh".
OK, this is working properly:
root@z6:/srv/chroot> chroot
Le 12/05/2022 à 17:51, John Paul Adrian Glaubitz a écrit :
On 5/12/22 17:45, Laurent Vivier wrote:
No, the 'F' means 'fix-binary':
The interpreter is loaded in memory once when the binfmt_misc is configured
(when
the configuration is written to /proc/sys/fs/binfmt_misc/register) from the host
On 5/12/22 17:45, Laurent Vivier wrote:
> No, the 'F' means 'fix-binary':
>
> The interpreter is loaded in memory once when the binfmt_misc is configured
> (when
> the configuration is written to /proc/sys/fs/binfmt_misc/register) from the
> host
> filesystem. So you don't need to put it in the
Le 12/05/2022 à 17:41, John Paul Adrian Glaubitz a écrit :
Hi Laurent!
The issue can be reproduced on a freshly installed Debian system.
Is the problem the additional "F" flag?
glaubitz@z6:/tmp/test> cat /proc/sys/fs/binfmt_misc/qemu-m68k
enabled
interpreter /usr/libexec/qemu-binfmt/m68k-binfm
Hi Laurent!
The issue can be reproduced on a freshly installed Debian system.
Is the problem the additional "F" flag?
glaubitz@z6:/tmp/test> cat /proc/sys/fs/binfmt_misc/qemu-m68k
enabled
interpreter /usr/libexec/qemu-binfmt/m68k-binfmt-P
flags: POCF
offset 0
magic 7f454c46010201000
7 matches
Mail list logo
