[knc1]

Originally Posted by geekmaster

Working on it...

I am sure I ran *something* on my K1 after copying it to a user partition, though I think it was /mnt/mmc (the SD card, which I stopped using because SO SLOW to eject from PC when mounted). As I recall, busybox did not run but OTHER binaries did work.

Anyway, to specifically answer your question, I copied busybox to /mnt/us/bin and ran it -- not working.

Code in install script:

echo =====[ cat /proc/cpuinfo ]=====
cat /proc/cpuinfo
echo =====[ uname -r ]=====
uname -r
echo =====[ cp /bin/busybox /mnt/us/bin ]=====
cp /bin/busybox /mnt/us/bin
echo =====[ /mnt/us/busybox ]=====
/mnt/us/busybox
echo =====

Output from that code:

=====[ cat /proc/cpuinfo ]=====
Processor    : XScale-PXA255 rev 6 (v5l)
BogoMIPS    : 99.32
Features    : swp half thumb fastmult edsp 
CPU implementer    : 0x69
CPU architecture: 5TE
CPU variant    : 0x0
CPU part    : 0x2d0
CPU revision    : 6
Cache type    : undefined 5
Cache clean    : undefined 5
Cache lockdown    : undefined 5
Cache format    : Harvard
I size        : 32768
I assoc        : 32
I line length    : 32
I sets        : 32
D size        : 32768
D assoc        : 32
D line length    : 32
D sets        : 32

Hardware    : Fiona Platform
Revision    : 0009
Serial        : "B001************"
=====[ uname -r ]=====
2.6.10-lab126
=====[ cp /bin/busybox /mnt/us/bin ]=====
=====[ /mnt/us/busybox ]=====
/mnt/us/RUNME.sh: 72: /mnt/us/busybox: not found
=====

And yes, I did verify that busybox is in the bin folder on my userstore, so the "not found" may refer to a library it cannot find when it is moved. Perhaps it is looking RELATIVE to its original path?

The Busybox in the file set you posted for me **IS** a static binary, it is completely stand-alone (except for the kernel calls it makes).

So if you testing above on the same system you took my file set from -
then we have made progress.

The reason your compiled binaries do not run is not **entirely** the fault of their build - it is where in the K1's filesystem they are run from (we just proved that by moving Busybox to /mnt/us/ and seeing it fail).

First thing - make the K1's Busybox run from /mnt/us - - -
There are three things to check:
Your BB is set-group-id and set-user-id -
Remove those control bits (one at a time, using chmod) and see if one or more of them is stopping BB from running on /mnt/us.

Translation:
/mnt/us might be mounted with the no-suid and/or no-sgid options.

That is two of the three - -
Now the third may be a bit tricky -
Try running:
sh -c /mnt/us/busybox
(Which might or might not work-around any no-exec mount option. This is used in our jailbreaks to work-around the NO_EXEC system flag.)