Life has been "interesting" as of late... but I've made the effort to get back into looking at tomtom navigator (TTN) running on zaurus.
The first step was to take the ttsystem file and split it, using the tools from opentom, and then copy the files into /home/tomtom. TTN uses busybox for many command, but uses a different libc. After briefly trying various tricks with LD_LIBRARY_PATH etc, I was unable to run the commands, so I resorted to "chroot /home/tomtom bin/sh", which gave me a working shell.
The TTN linux distro runs a command called "ttn", which does all the work; it's this program that the early OpenTom programs replaced. Incidentally, OpenTom is coming along very well, even managing to allow you to "dual boot" their media player and TT's navigation s/w, and maybe even switch from one to other. Anyway, I digress.
The first attempt to run the ttn binary caused a spew of errors, and then it killed the Z stone dead; at first I panicked as it wouldn't turn on again, but unplugging from USB and pulling the battery sorted that.
I started fixing the errors reported to console (luckily for us, TT tell us all sorts of useful things). Most of them were missing devices, so I copied them over from the Z and added links (TTN wants framebuffer device as /dev/fb for example).
I then removed reboot and other "dangerous" commands, replacing with a script to indicate they were called. Didn't stop ttn killing the Z dead!
"strings ttn" reveals some very interesting tricks to make ttn completely self-sustained - dialling scripts and all sorts.
I was able to copy a few useful Z commands to the TTN image, such as "ldd" to see what it was doing.
So far, I've gotten ttn to open the framebuffer and the touchscreen, and next I need to spoof the sdcard!