Thread: Kobo Start Menu 08
View Single Post
Old 01-27-2017, 04:18 AM   #425
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by tshering View Post
The assumption is that in any kind of update (forced/required) the step of extracting the content of KoboRoot.tgz and copying files from the upgrade folder is done by the rcS. If this is the case, KSM can prevent this from happening without consent of the user. So nickel can download the update zip, extract KoboRoot.tgz and so on from it, can decide whether there is enough space to install it, but not more. My question is whether the assumption holds.
I'm pretty sure nothing has changed with handling of KoboRoot.tgz. I have only noticed one possible change in the way the beta's I've been getting have been installed. The change is that two or three times, the device has started the install without prompting. This might be the "UpgradeForced", but the other devices did prompt. And, each time, the device went to sleep during the download. I have a feeling that waking triggered the install, but I haven't done the experiments to prove it.
davidfor is offline   Reply With Quote