I'm having a problem getting busybox to run anything else other than itself. I'm using BusyBox v1.19.4. I'm 100% sure this is NOT a busybox bug... but something I'm doing wrong on my end, and I was looking to get pointed into the right direction so I can resolve my problem.

So far this system is nothing more than a Kernel with AUFS patching and Busybox running in an initrd. I'm using kernel 3.7.7 right now. The system boots fine, and busybox starts and runs successfully. I can use any of the busybox commands without issue. however when I try to start any other program, like another shell for example, zsh, bash, etc. Busybox returns that the command is not found. However I can navigate the filesystem and see the files are there with the proper permissions. See: http://q5sys.info/busybox-issue/error2.png In fact even if I chmod zsh to 777, I still cant run it. See: http://q5sys.info/busybox-issue/error3.png So chmod sees the file, and can successfully change its permissions, but BusyBox cant run it.

I'm guessing this is something simple I'm missing, but when I've tried to search google, I dont come up with anything applicable. Can you at the least give me an idea of what I should be searching for to find the solution to my problem.

As a side note, I tried upgrading BusyBox to v1.20.2 and I get alias issues, see: http://q5sys.info/busybox-issue/error.png
Did I miss something in the release notes for v1.20?

At this point of development I'm doing testing within virtualbox v 4.2.6 r82870, but since I'm certain this is a configuration issue on my end and not a bug issue, I dont think that should matter at all.

Thanks in advance for any info you can provide.
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to