Quote:
Originally Posted by NiLuJe
@geekmaster: You mentioned the lack of /var, which might indeed mean that, unlike on newer devices, otaup doesn't cleanup after itself  .
That doesn't really explain why those scripts suddenly run for no apparent reason (unless they never got killed?), but, still ;p. |
They do not loop, and installs are unpacked into /tmp/ which I believe is one of the 10 RAM disks. It probably disappears if you do a hard reset, not just when it is in screensaver mode (mostly asleep). Turning the power switch off (which blanks the screen) does not prevent the install script running again after it goes into and comes out of screensaver mode. Strangely, though my script does not loop (just one pass and return 0, and it is in a directly name with unique process ID, it still RERUNS now and then. Also, when plugged into USB, it sometimes awakes unexpectly and runs the script before displaying the home screen.
K1 has enough differences to be interesting, including no var, no apparent keystores in the mounted file systems, and lots of unmounted partitions. Also, it uses the Samsung XRS flash manager, with bml0 (block management) devices that do not do write wear-levelling (only mounted read-only) and stl0 (sector translation layer) overlays with write wear-levelling and bad block removal (and spare sectors to replace them). Difficult to decide which level (raw or translated) to backup and restore, with potential device dependence (depending on flash wear and sector relocation). And an intel SoC instead of FreeScale (now NXP). Interestingly, the /test/ folder on my K3 seems to support a wide range of devices including K1 and K5, newer than K3, based on contained comments. I also have a /test/ folder on one of my K4 devices. I will eventually try copying K3 /test/ to my K1...
I suppose I should document this stuff in an independent thread, even though it is a derivative of this thread because my explorations began with kindletool. And we seem to be missing a K1 prefix and prefix index?