[geekmaster]

Originally Posted by kaminkatze

I used this kite script

#!/bin/sh
/mnt/us/bin/tinysh &

to start tinysh and modified

[[ $K -eq $ENT ]]&& shcmd && continue

to something like

if [[ $K -eq $ENT ]]; then
  [[ $CMD == "quit" ]] && exit
  shcmd && continue
fi

so I can exit tinysh.

That looks good, except now you cannot send "quit" to the shell or to a linux program. I would use something unusual but easy to type, like ".quit.", or use an undefined button (such as Menu) as a "command" key (which sets a "command" flag). Then at Enter key processing, exit if command flag set AND "quit" in CMD buffer. Remember to clear the command flag at end of Enter key processing. A "command" button could support other "local" options as well, such as clearing or refreshing the display, or even executing command macros to save typing long commands.

Remember that the K3 and earlier already have a nicer onscreen shell (I recommend myts-7). This script was meant to be used in special cases, like during debricking, but especially as an example of what you CAN do with a shell script, using ONLY stuff that is already built-in. And modifying this as you are doing is a GREAT learning experience.

P.S. How did you get tinysh working in kite, instead of only telnet as you had previously reported?