Quote:
Originally Posted by igorsk
Okay, so I did some investigation (mostly consisting of reading S20libromount script  ) and here's the summary:
/opt, /opt1/keys and /opt1/info are mounted from cramfs images, meaning they're read-only.
/opt0 and /Data use jffs2 which is writable
/etc and /var are copied to ramdisk (created in /dev/shm/) and remounted at /, so we can't access the original dirs.
|
Yeah, that's a hassle. We can't change any of the startup scripts, I guess, because we would have to unmount the copies from the /dev/shm first before we can overwrite the originals. Perhaps there is a way to force running some sort of a script on the Reader, but that would clearly be a "security breach", so I suspect Sony would try to close that loophole (assuming they don't want us to hack into their device, which may be an incorrect assumption, but this is not a Nokia 770 for you).
Otherwise Mr.
gseryakov's idea would have been implementable, if space-costly - make your own copy of /opt (if the USB Reader interface protocol allows us to create directories in the Reader's filesystem, which is not yet done in ebook.py, or just copy a tar file and untar it locally) and make a mod in one of the rc scripts to overmount /opt (or perhaps even only /opt/sony/ebook/FONT) on boot-up. But first we would have to come up with a way to execute a program of our own in the device's OS.
I suspect Sony's way of doing the Software upgrades assumes a certain authentication procedure, and then a special set of commands which will (a) load the updates into a writable directory in the Reader (b) tell the local service to perform a software update/reflash from a local copy.
If Librie-I allowed a hack to update firmware or install applications, it is possible that the same or similar hack still works for the current Reader. Chances are, the flash updater is proprietary, not open source.