Quote:
Originally Posted by knc1
Re-built Busybox with inetd enabled.
It would be better to use auFS than the posted "file overlay hack" but the kernel(s) in the Kindle(s) are too old for that.
Using auFS requires a newer kernel (a big project, even if only considering the testing that is involved) so that can wait for a later release of the "restore it" tool.
|
The nice thing about the method I am proposing is that you can ALWAYS to back to a "factory_fresh" set of disk images (or as close as we have to that). This makes experimentation with major firmware changes (even TOTAL replacement) much less of a problem. If you brick it, just do a "system restore" back to whatever saved firmware images you want. To help with this, I want a differential backup system, where you can restore from the last full backup, then step forward doing differential restores until you are at the backup point in time that you want. I want a GUI with a timeline slider for this, with markers for all the available restore points...
Anyway, that is what I want, even if I have to build it all myself...
I am studying how to flash large images in segments now, so we do not need the data.tar.gz and RUNME.sh step. I am hoping to provide a "One Button Solution" that will do everything for you after you decide what you want...