View Single Post
Old 02-13-2013, 08:36 AM   #4
dsmid
Linux devotee
dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.
 
dsmid's Avatar
 
Posts: 598
Karma: 2069047
Join Date: Feb 2011
Device: Kindle 3, Kindle 4B, Kindle PW2
Quote:
Originally Posted by knc1 View Post
Does this also prevent the updater in the initramfs from running when the update file is present during a full reboot (cold start)?

If unknown, please test for that and report back.
Well, when I left an update from Amazon in the user store (Update_1615370055_1813030025.bin) and rebooted, it didn't do anything.
On the other hand, doing the same thing with a hack (update_loc_cz_4.1r62_k4_install.bin) gave me "Update error 3" on boot.
I suppose that the initramfs beast is looking for update files with a lowercase prefix of update_ or is silently ignoring Amazon signed packages that are not full updates.
I don't know how would a full update package behave on reboot though (there are no such updates for my Kindle models). It may get installed.

The problem is that deleting/damaging the update file would trigger redownloading and I'm trying to avoid that.
Maybe an init script purging any update files in user store scheduled to launch when Kindle is shutting down would solve the problem.

Last edited by dsmid; 02-13-2013 at 08:44 AM.
dsmid is offline   Reply With Quote