Find Your Device:
Or Continue to Thread: [2015/03/07] BotBrew: *nix too…
1st April 2012, 05:16 AM |#69  
OP Retired Recognized Developer
Thanks Meter: 195
I'd like to explain how the upcoming BotBrew release works. All this is covered in the manual as well.

Firstly, it installs packages to a directory named /data/botbrew. It also sets up a bind mount to /botbrew. This means that it is no longer possible to directly call the programs that you install. Two mechanisms are in place to remedy that:
  • a helper script /system/bin/botbrew to point PATH to /botbrew/bin
  • a helper script /system/bin/ldimport to link libraries from /botbrew/lib to /system/lib

So if you're connected via adb or using any of various terminal apps, there are two ways to run your programs:
  1. prefix your commands with botbrew; for example, botbrew nmap -v -A
  2. run botbrew (or as a shorthand, bbsh) before issuing commands

If you've installed dropbear and are connected using SSH, the new PATH setting is in effect, so you do not need to prefix your commands.

In most cases, you don't need to use ldimport, since the BotBrew GUI runs it for you. If you installed packages using the command line, you'd need to run it manually as root, with a writable /system.

Secondly, it comes with a new service supervisor powered by runit. Mobile devices are resource-constrained, so it's not always a good idea to run background services all the time. The supervisor shows you a list of services you have installed, and lets you turn each one on and off by tapping the button to the left. If you turn off the supervisor, you stop all the services too.

I hope this helps.
Last edited by inportb; 9th April 2012 at 06:51 PM.
The Following User Says Thank You to inportb For This Useful Post: [ View ]