Quote:
Originally Posted by twobob
Is there a "prefer real binaries over scripts" type thing going on?
confused.
|
That is an effect of how the K3's original Busybox was configured.
Previously reported by geekmaster.
What is happening, is the command line processor (ash) **IS** busybox, and the built-in is being detected / selected **before** any path search is made.
Hmm...
There might be a "perfer built-ins" config option in the original Busybox build that did that.
You can delete the sym-link to the original Busybox to fix that, if willing to alter the system files.
Note:
When the /mnt/us part of the file tree is displayed to the user in "storage mode" - I don't think that the main system can access it.
Note 2:
The above was one of the reasons behind my wanting to try the various shared file system on the K3 -
So that "user storage" could be both exported and used internally, concurrently, rather than switched between internal and external use.