Quote:
Originally Posted by davidfor
Your looking at code that is executed a long time after the problem that is being discussed occurs.
|
Hmm, pretty sure it is the right place. On startup (or disconnect, etc.), init calls rcS, which is in /etc/init.d. As part of that, there is a check to see if KoboRoot.tgz and upgrade folder exist in .kobo
If so, it untars KoboRoot.tgz, and calls upgrade-wifi.sh. In that script, at the start, it does the MD5 check - which, if it fails, causes the upgrade process to abort immediately. If its fine (or the md5 file doesn't exist), the firmware is applied in generic-upgrade.sh (using dd, etc., that george.talusan mentioned as a way to fix the Glos that were bricked). So it'd be easy to add a few lines in to check the version.
Quote:
Originally Posted by davidfor
Of course, there already is code that checks if the right firmware is being loaded. It is the code in the desktop app or WiFi download or maybe on the download server that makes sure the right firmware file is downloaded. Personally, I am happy with this mechanism. And I am happy that if I want to bypass this and take the risk I can try something else. But, that is my decision.
|
On the face of it, I totally agree
Kobo shouldn't have to go out of its way to prevent stupid user errors, especially "unauthorized", stuff we've been warned against doing, etc... but this really seems like an easy fix, something that should take a few minutes to add in. And if someone screwed up the logic server side, somewhere, it'd be an extra easy check.