bash for kindle

[fbdev]

i couldn't stand busybox; so i built bash.
in case you don't feel like building it yourself, here's the binary.
(source)

md5:
4b5000f232e96db8aba5722ee90aff7a bash.tar.bz2

sha512:
0d59e498dfd576a48f2294a81e61665ca5e402c254add6d24a 79aeb3379971bfcfc6db5aee2ec8a425dbdfb0ccdd0db425fb 786d0ad66599c9c0ac4a13deb9b2 bash.tar.bz2

[aquarat]

Thanks fbdev!

What toolchain did you use to compile it ?

[aquarat]

I worked out how to cross compile for the Kindle... so here's the nano editor if anyone wants it.

There are two bz2 files, just merge their contents with the root filesystem (you'll need to type "mntroot rw" first).

b96a6ee4c5d0b624baaf03729e616857 ncurses.tar.bz2
6bdc743d751b0d779dc10546b88ead58 nano.tar.bz2

[proDOOMman]

Do you know about ipkg?

[jonj678]

You sir, are a very good man indeed. The frustration of writing and debugging a script in bash, only to find that busybox's ash just doesn't know what to do with it is considerable. This is a much better alternative than learning the bourne shell. Thank you

[fbdev]

it was compiled with scratchbox.

it's only the executable, so if i'm going to use it i just drop it into /tmp and add it to /tmp/root/.profile like so:

if test $SHELL = "/bin/sh" && test -x /tmp/bash; then
export SHELL=/bin/bash
exec /tmp/bash
fi

[ryran]

Oh this is so nice.

[xueyou2]

Originally Posted by aquarat

I worked out how to cross compile for the Kindle... so here's the nano editor if anyone wants it.

There are two bz2 files, just merge their contents with the root filesystem (you'll need to type "mntroot rw" first).

b96a6ee4c5d0b624baaf03729e616857 ncurses.tar.bz2
6bdc743d751b0d779dc10546b88ead58 nano.tar.bz2

I am a freshman in linux.so can you tell me how to merge their contents with the root filesystem ?
And how to install it in kindle.I have a terminal in kindle 3.3 now.
Please just in detail.

[aditya3098]

Nice module linux.so

[hawhill]

xueyou2: Do not touch the root filesystem if you don't know what you are doing.

Better stay in the document partition and install there. Just put the binaries somewhere and point the dynamic linker to where your libraries are (if the binary comes with any) via LD_LIBRARY_PATH environment setting.

[geekmaster]

Originally Posted by hawhill

xueyou2: Do not touch the root filesystem if you don't know what you are doing.

Better stay in the document partition and install there. Just put the binaries somewhere and point the dynamic linker to where your libraries are (if the binary comes with any) via LD_LIBRARY_PATH environment setting.

Even IF you know what you are doing, there are still some rules you need to follow:

You can "temporarily merge" things into the root fs using a "bind mount", which temporarily "replaces" a file on root with a file on mmc. See how I do that to replace /usr/lib/libc.so in my "tccmake" script used in my "simple tcc guide" thread.

Also, adding additional symlinks to root that point to files on /mnt/us is generally safe, but DO NOT link files into /etc/upstart until they are fully tested. An upstart script that returns error status can prevent OTHER critical scripts from loading during startup. And beware that symlinks are permanent, unlike bind mounts.

The IMPORTANT thing is to not use significant space on the root fs, which may be needed for firmware updates.

Unsafe changes to the root fs can brick your kindle (but we know how to fix that -- just rewrite the root fs partition).

[xueyou2]

Originally Posted by geekmaster

Even IF you know what you are doing, there are still some rules you need to follow:

You can "temporarily merge" things into the root fs using a "bind mount", which temporarily "replaces" a file on root with a file on mmc. See how I do that to replace /usr/lib/libc.so in my "tccmake" script using in my "simple tcc guide" thread.

Also, adding additional symlinks to root that point to files on /mnt/us is generally safe, but DO NOT link files into /etc/upstart until they are fully tested. An upstart script that returns error status can prevent OTHER critical scripts from loading during startup. And beware that symlinks are permanent, unlike bind mounts.

The IMPORTANT thing is to not use significant space on the root fs, which may be needed for firmware updates.

Unsafe changes to the root fs can brick your kindle (but we know how to fix that -- just rewrite the root fs partition).

I feel powerful because of 'but we know how to fix that'.
But I find that I need to study linux first .Then ....
Thank you for help.

[thatworkshop]

A quick question my friends: How can one replace busybox with bash? Is it safe?

[geekmaster]

Originally Posted by cscat

A quick question my friends: How can one replace busybox with bash? Is it safe?

You do not replace anything. Just run bash and it opens up a bash shell inside the busybox ash shell, in the same terminal window. If you type "exit" you leave bash and are back in busybox.

[thatworkshop]

Originally Posted by geekmaster

You do not replace anything. Just run bash and it opens up a bash shell inside the busybox ash shell, in the same terminal window. If you type "exit" you leave bash and are back in busybox.

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!