Hmm...Hi @jj_0
You said corretly. I don't want to loose the feeling of doing it by myself.
Things to check.
- 1) whether the file is aarch64 ==> Yes
2) whether it is executable (has the x attribute set) ==> Yes
3) whether it is fully readable. ==> How can I check this ?Let me know what else I need to figure out in the process of analysis of /sbin/init file.Code:
vivek@vivek-virtual-machine:~/raspi-5/buildroot/output$ file target/bin/busybox target/bin/busybox: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, stripped
I would do something like md5sum sbin/init or as I mentioned before chroot into your rootfs from a PiOS booted system and see if any of the binaries (at least your busybox) runs in the chroot.
You could even emulate booting with systemd-nspawn -bD <path to your rootfs> but then it uses the Pi's kernel of course.
Statistics: Posted by jj_0 — Sun Aug 03, 2025 10:36 am