Bugzilla – Bug 11768
Consolidate copying and verifying firmware into one step
Last modified: 2009-09-08 09:31:39 UTC
In my experience, the way the Fab4 presents the firmware update process is a bit unusual. The typical upgrade process with most consumer network devices presents this as a single step. I feel that you should make it as familiar as possible for the typical user. Functionally identical. Just presented differently.
Not quite a dupe, but related to bug 10642.
I think it makes sense to explain to the user that it's downloading, which gives them a sense for how long it might take. Verifying would be a separate step, which shouldn't take long at all. So maybe we just call it Downloading and then Verifying? What do you think, Matt?
I don't quite follow the logic, but if it must be two steps, how about Downloading and then Installing?
I prefer showing the "Downloading" part separately, "Installing" isn't exactly correct, but is more understandable.
Totally fine with this, I agree the language is more familiar to typical users...
EN strings changed in r5289 to "Downloading" and "Installing". Other languages will remain as is through MP.
Just to be clear about how this actually works, the "downloading" stage downloads _and_ saves the upgrade to flash. "verifying" performs a checksum on the image in flash to confirm it's ok before rebooting. The new names are not correct, and could be misleading in the case of an error. I don't really care about this, but if someone does they should reopen the bug.
(In reply to comment #7) > Just to be clear about how this actually works, the "downloading" stage > downloads _and_ saves the upgrade to flash. "verifying" performs a checksum on > the image in flash to confirm it's ok before rebooting. What happens if the checksum fails? Does it somehow retain the old firmware or does the unit potentially become a brick?
JJ: fyi- like on Controller, Fab4 retains two copies of the firmware update images, so in the case of some corruption, the previous version is always available.
(In reply to comment #9) > JJ: fyi- like on Controller, Fab4 retains two copies of the firmware update > images, so in the case of some corruption, the previous version is always > available. Then I would contend that "installing" for the second phase is technically correct, as well as more understandable. It's not installed until both verified and then switched to. To the end-user, whether the image has been loaded into flash is incidental until it's actually put into use.