Open CzBiX opened 12 years ago
The BotBrew seed package does ship /bin/busybox
and a symlink /usr/lib/busybox/tr
to it; and PATH
usually includes /usr/lib/busybox
. Is this somehow not the case in your setup?
my busybox is in /system/bin/
and I have not found /usr/lib/busybox/
even /usr/
in my phone.
busybox
usually be put in the /system/bin/
, like CM or some apps that can get root for device.
except user install busybox
himself with the Busybox Install Apps.
why not just exec busybox tr ...
in shell to do that. busybox can be in the PATH or download by BotBrew.
It would be /data/botbrew-basil/usr/lib/busybox
if you bootstrapped to the default path of /data/botbrew-basil
. And busybox
itself would be /data/botbrew-basil/bin/busybox
. So the actual paths depend on where you selected to bootstrap BotBrew, but both locations should be accessible via PATH
.
Since we cannot assume that the user has a working busybox
, we always bring our own. And we set up the appropriate symlinks and PATH
to make it work. So something might have gone awry right there.
so, how about use tr
directly with busybox tr
, and without create symlinks for tr
.
It's a good suggestion, but I'm not sure if that fixes the actual problem. For busybox tr
to work, busybox
must be available via PATH
. And if busybox
is available, then so should the tr
symlink. So, should we use the full path /bin/busybox
? I'm thinking that the code in jni/init/init.c
isn't setting PATH
correctly.
we cannot assume that the user has a working busybox
and tr
, so use the full path to avoid unexpected issues.
when I install botbrew, it was reported that error information what's in the title, and I found the error "postinst: tr not found", so, I run
ln -s busybox tr
myself, it's works well now.