Tiny Core Base > TCB Talk

binfmt_misc

(1/3) > >>

cparke:
I want to use TinyCore (x86) to chroot into the TC Raspberry Pi rootfs via qemu-arm. 

To do this requires binfmt_misc, which appears to be entirely missing from TinyCore's kernel and the extensions library (I think this feature needs to be either compiled directly into the kernel with the CONFIG_BINFMT_MISC option flag, or maybe can be installed as a kernel module?)

Any suggestions on how I could enable binfmt_misc in TC 16?

Juanito:
If you look here:

http://tinycorelinux.net/16.x/x86/release/src/kernel/config-6.12.11-tinycore

# CONFIG_BINFMT_MISC is not set

..so you would need to recompile the tinycore kernel.

That being said, the last time I tried to use qemu with PiCore, it didn't work very well.

cparke:
That seems pretty involved, as described in this Wiki page:
https://wiki.tinycorelinux.net/doku.php?id=wiki:custom_kernel

Is it that expensive to set the option CONFIG_BINFMT_MISC=m so this could be a simpler process of just compiling the desired kernel module, or even so a .tcem (do those still exist?) could be offered to install this feature seemlessly?

To make such a build compatible with the rest of Tinycore 16 and its tcem's, I need to pull the exact same version of the kernel from kernel.org and apply all of the TC patches?

Juanito:
You can use the config and the patched source from here:

http://tinycorelinux.net/16.x/x86/release/src/kernel/

Sometimes you can use a new kernel module without changing anything else (i.e. you can make an extension of it) and sometimes a new vmlinuz is needed.

cparke:
Was the TC 16.0 kernel built under TC 15.0 environment or some other distro?

Do I rename the 'config-6.12.11-tinycore' to '.config' and then run 'make oldconfig' to initially transfer over all the TC options?

Do I have to re-apply the patches, or have they already been applied and just there for reference?

Navigation

[0] Message Index

[#] Next page