View Single Post
Old 05-11-2016, 09:25 AM   #92
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by geekmaster View Post
I do have binfmt and qemu-static in my linux mint, and some K1 binaries run fine. Copying the K1 /bin to my chroot makes chroot fail (cannot find /bin/bash) which may be a problem with the K1 bash symlink. I could try to copy busybox and rename it as bash, instead of a symlink...
Depending on how the chroot was populated, if you don't specify the name of the shell as an argument to the chroot call, then it will try to find /bin/bash.

A sysmlink from /bin/bash to /bin/sh will work, if /bin/sh is linked to busybox (two levels of symlinks).

or
chroot '/bin/busybox sh' username (default 'root')

or
you don't have /proc mounted inside of the chroot.

this build of busybox acts as if it was built to look for: /proc/self
in its applet name decode.
But I haven't straced it to be sure.

= = = =

Stay away from Windows for awhile - it is poisoning your mind.
knc1 is offline   Reply With Quote