Quote:
Originally Posted by geekmaster
Perhaps you could use some code from the OpenWrt project, which uses a COW file system  .
The problem with a general overlay filesystem is that hacks would still have to be coordinated or they could damage each other due to namespace collisions  .
Even simple launchpad key assignments risk hijacking by other apps, which is especially easy to do since the launchpad folder supports multiple .ini files. Either a .ini file could accidentally get replaced, or it could contain launch key assignments that are already in use in another .ini file. End users should not have to go in and compare and change all their .ini files to get them to work together -- that would be too much like the old days when plugging an ISA bus card into a PC meant removing all the other cards and changing their IRQ and address assignment jumper pins and DIP switches so that they could all work together (complicated by the fact that each card had a very limited supply of available settings, especially on 8-bit ISA)  .
I really like Yifan Lu's idea of each hack getting its own filesystem (but some hacks might need access to other hack file spaces). I would recommend a cloop mount except in cases where a compressed loop mount uses too much CPU for the application using it  .
Yifan Lu: If the kindle touch data dumps you want are in mmc, the mmc chip *could* be physically removed and read on an external computer (perhaps soldering the pins to a cheap microSD card adapter socket). Perhaps we could donate funds to get you a "sacrificial" kindle touch (I already donated $10 at your linked web page). Keep up the *great* work!  . |
I would try to get a serial connection going, but from what I read, it is hard to open the new kindles without breaking anything and voiding the warranty. That being said, if anyone has an already broken kindle touch, contact me.