The most intransigent problem with failed EFI firmware updates has been with the iMac Retina 5K 27-inch Late 2015, or iMac17,1. Some were attributed to the use of third-party memory or storage, although why any installer should take exception to perfectly legitimate hardware upgrades has never been explained or acknowledged by Apple. Then users started to report problems installing updates. Some years ago, this changed and firmware updates are only made available to users as part of a macOS or security update. In older versions of Mac OS X, Apple used to distribute firmware updates separately, with a special installer. The long-running saga of failed EFI firmware updates is a case in point. Apple has long taken pride that “it just works”, but seems to have convinced itself that is inviolate fact, and has become unable to consider what happens when it stops working. I’ve written repeatedly about the first two on all too many occasions, but in the last few weeks the third has become more prominent again with issues such as EFI firmware updating and the maintenance of APFS. These are intimately interrelated, as you can’t have any one of them without the support of the other two. maintenance procedures and tools, and maintainability in general. Three interrelated functions spring to mind in the context of macOS: When you’re developing an operating system, in particular, there’s a great deal more that needs to be built into the process. Like any other engineering discipline, there’s more to software engineering than just hands-on coding.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |