Re:How the Boeing 737 Max Disaster Looks to a Software Devel...
by nixass on Friday August 21, 2020 @10:23AM
(#24235109)
There must be post-checks or checklist to perform after the update. I doubt they go airborne with Gremlins under the hood (737MAX issues aside..)
[ Parent
| on HN ]
Re:How the Boeing 737 Max Disaster Looks to a Software Devel...
by Jtsummers on Friday August 21, 2020 @10:41AM
(#24235276)
Often, for software like this, you distribute a few pieces of data with the update. After it's installed the system runs and presents information like version number and the hash value of the binary (or binaries). You're supposed to verify these values as part of a checklist. Additionally, the primary host system can check that the hashed value presented is what it expects. How it handles it at that point may vary if it doesn't match, but at a minimum an error is displayed to the operators and stored in the logs. Since software isn't typically changed daily, this means verifying everything is updated once (update an LRU and update the corresponding portion of the host at the same time) and you're done for 6-18 months.