PeterPawn
commented
8 years ago - solved with b5542dc593f46d0569d0f4e464d9497332a23fec
- the sometimes different "blkid" command, which leads to unexpected behaviour of the script, was replaced with "peeping" into the image files (with "testvalue") and searching for known signatures
- the following commands are still used from vendor's firmware:
/bin/testvalue /sbin/update_kernel /bin/showshringbuf (for debug output)
- all other commands are contained within our archive file in the "bin" subdirectory
busybox mksquashfs[34] unsquashfs[34]
use the applets of the provided static Busybox binary as often as possible and call them with absolute path references to minimize the chances to call a wrong command/applet