There doesn't seem to be a copy of the Kindle 3.1 kernel config file on the internet yet. So I will put it online here. Also I will list a few interesting directories, like proc. This is just for documentation purposes and so people don't have to hack into the kindle to find out that e.g. though it has powertop, the kernel's support (timer_stats in /proc) is disables and so it's of no use. Check below for tons of information from the kindle root shell environment.

# Critical battery in millivolts. If the current voltage is
# less than or equals this, we won't let the system boot
_CRITBATT=`kdb get system/driver/charger/CONF_CRITBATTLEVEL`
_CRITBATT_DEFAULT=3460
_CRITCHARGE=4
_NOBATTCHECK_FILE="/mnt/us/system/nobattcheck"

# Normal run level
_NORMAL_RUNLEVEL=5

# Wait this many seconds before checkig voltage again
_WAIT_SECS=10

# This many iterations per minute. We log once per minute
_ITR_PER_MIN=6

BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as!

ps -AfWell, in my case the parent process is: "/usr/bin browserd"A defunct process normally means a process exited that has a parent but the parent never waited for the child process.I guess that's one of the reason why the browser is experimental :P

sh zombie is probably there to keep /usr/bin/browserd alive (zombie brings browserd back when browserd process is killed).I managed to kill 'em both by killing zombie right after killing browserd (kill $browser_pid';kill $zombie_pid). But this leaded to hanged behaviour of the kindle. Restart of device solved it. I can see that browserd process consumes about 7-10% of RAM in TERMINATED state right after web browser is closed. Killing of browserd process leads to bringing new browserd process back (thanks to zombie) with consumption of about 3.3 % of RAM in STOPPED state.