Coercing the SuSE Studio build system to install Debian in a chroot environment is a bit of a challenge.
You would think that they only wanted you to install SuSE software.
Today's plan:
Three users (in addition to 'root'):
tux -> logs into the host side of the system (they can schroot into either of the build systems).
The build systems (currently) will be 32bit, armel (soft float) exclusively, regardless of the host being either 32bit or 64bit.
tuxn -> logs into the native build (chrooted) system (they can exit out of it).
tuxc -> logs into the cross-compile build (chrooted) system (they can exit out of it).
In addition to being a 32bit environment, the chrooted systems will be old enough versions that there should not be any conflicts between the version of libc they are running and the version(s) of libc that the Kindles are (or where) running).
I think that means I have to support back to 5.3.7.3 - the most recent firmware run by the oldest touchscreen Kindle.
Once that is done -
If there is demand enough, I could include one of twobob's development environments that are old enough to build for at least some of the keyboard models.
Currently, from the amount of feed back I see -
This project will grow cold as soon as I have an image that suits myself.
If there are not users to support, why spend time going past the 'works for me' stage.