bash for kindle

[geekmaster]

Originally Posted by cscat

What I want is to run my custom scripts with bash instead of busybox... What should I do for this? just make a symbolic link from this bash to /bin/bash (which already exists and is a symbolic link to busybox)?

Edit: I did the above thing and then ran this code just to check I'm actually using bash not busybox.

test.sh

#!/bin/bash
history

but no luck!

Just point your custom scripts at YOUR bash:
#!/mnt/us/bin/bash

Or feed them to bash:
/mnt/us/bin/bash myscript.sh

That way they will run in bash even if you launch them from a busybox shell (no need to start a bash shell).

[hawhill]

And by all means, restore the original /bin/bash symlink. The /mnt/us is not necessarily up and running from reboot on (but the root file system should be), so you have a symlink pointing to nowhere at boot, breaking all system scripts that use /bin/bash.

If I am not mistaken, the easiest approach is to use "#!/usr/bin/env bash" and set an appropriate PATH. That will leave scripts compatible on many platforms.

[thatworkshop]

Originally Posted by hawhill

And by all means, restore the original /bin/bash symlink. The /mnt/us is not necessarily up and running from reboot on (but the root file system should be), so you have a symlink pointing to nowhere at boot, breaking all system scripts that use /bin/bash.

Thanks hawhill. You taught me something today. And obviously thanks geekmaster.

Originally Posted by hawhill

If I am not mistaken, the easiest approach is to use "#!/usr/bin/env bash" and set an appropriate PATH. That will leave scripts compatible on many platforms.

Well if I want to change my PATH, I'd suppose I have to add the path at the beginning, eg. like this:

/mnt/us/bin:/usr/local/bin:/bin:/usr/bin:/usr/sbin:/sbin

And by doing this, at boot time bash will kick in instead of busybox. And your proposed problem will still exist. Am I wrong?

EDIT: I'm asking because I don't want to do any harm to my only Kindle again.

[hawhill]

Oh, I was suggesting to set the PATH only for the terminals you use. I think someone else who can actually tell how things are organized on a KTouch could go into details and e.g. explain how to set session settings.

And it's in fact a bit different situation as for consequences for the boot sequence: Non-existing paths are ignored. Bash won't kick in, however, since other scripts will probably use absolute path (#!/bin/bash) instead of that "env" trick (which will search the PATH for the named executable).