MobileRead Forums - View Single Post

geekmaster · 05-13-2016, 12:26 PM

A script just finished that had been running all night, scanning all my mounted drives using "file" to search for ARM static executables. Interestingly, the vast majority of ARM static programs are "ldconfig", which makes sense in that you cannot dynamically load the loader configuration utility with an unconfigured loader.

I did find a few static busybox versions, including a busybox-4l which does not show any EABI info or linux version info, which might be worth trying (though I suspect I did try it at one point and it failed, but I will try again).

It also looks like all the statically-linked apps copied from K1 firmware (regardless of firmware version) specify "for GNU/Linux 2.0.0" which is much older than any other ARM static app on my storage devices (with most non-K1 stuff specifying 2.4.x or 2.6.x).

05-13-2016, 12:26 PM	#155
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773670 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	A script just finished that had been running all night, scanning all my mounted drives using "file" to search for ARM static executables. Interestingly, the vast majority of ARM static programs are "ldconfig", which makes sense in that you cannot dynamically load the loader configuration utility with an unconfigured loader. I did find a few static busybox versions, including a busybox-4l which does not show any EABI info or linux version info, which might be worth trying (though I suspect I did try it at one point and it failed, but I will try again). It also looks like all the statically-linked apps copied from K1 firmware (regardless of firmware version) specify "for GNU/Linux 2.0.0" which is much older than any other ARM static app on my storage devices (with most non-K1 stuff specifying 2.4.x or 2.6.x). Last edited by geekmaster; 05-13-2016 at 12:43 PM.