Those two Daemons are the culprits, that's right. But removing the control panel extensions did not remove their files, they kept doing their now useless tasks and crashing. So it might still be considered helpful to remove them manually...With EasyFind or FindAnyFile, keyword(s) - dosdude1 and dd1 will find the Launch Daemons. Right clicking on the two Control Panes removes them. Patch Updater in Utility ƒ can be deleted. 😎
The AppleInternal bit definitely breaks all Big Sur OTA updates, but not updates for anything else (ie. Safari, etc). This is because when the AppleInternal bit is set, the process involved in Big Sur OTAs switches to using an internal server (which has no DNS entry on public DNS), and since that server is not publicly available, it fails. (Redirecting it back to the normal server works fine.) However, things like Safari use a different update mechanism, and they're not affected. Catalina and lower aren't affected either, as they exclusively use the other mechanism - only Big Sur OTAs are broken (whether deltas or the full 12GB downloads that I like to call the "full bundle", for lack of a better term).
I'll check authenticated root/0x800 later, but I doubt it'll change anything. That bit's probably just a red herring with the real cause being broken seal.
0x800
is not so much that it automatically breaks incremental updates, as that it makes it too easy to break the seal on the OS, perhaps inadvertently, and then obv. you won't get an incremental update, at least not next update. Does that sound about right? (If so, that closes the issue - or rather resolves all my confusions, anyway - thanks! Bonjour,
Well no, when I said I missed something.
It's done and it works perfectly, thanks. 👍 😉
View attachment 1786164
Those two Daemons are the culprits, that's right. But removing the control panel extensions did not remove their files, they kept doing their now useless tasks and crashing. So it might still be considered helpful to remove them manually...
Amid the speculation there is this: https://eclecticlight.co/2021/06/01/which-macs-will-be-officially-supported-by-macos-12/Yes, also waiting to see what will happen with macOS 12.
There is talk of more mac models officially supported will drop off. Hope OCLP will come to the rescue.
Also hope that 2012-13 models will make it across to macOS 12 with OCLP.
Somewhere in the depth of all the posts here there was this „clean installation„ recommendation. It is a fairy tail that one can survive several dozens or system software updates starting at 10.8 or before and end up in the very same state as doing a clean installation with the latest 11.4.KnockKnock v.2.3.0 was useful, too in the quest.
A very harsh cut-off if it eventuates would seem to suggest that Mac OS 12 could be the last Mac OS to run on Intel Macs.Amid the speculation there is this: https://eclecticlight.co/2021/06/01/which-macs-will-be-officially-supported-by-macos-12/
So far, haven't had that problem on any of the unsupported Macs. But will keep it in mind, thanks. 11.5b1 OTA works great after the purge, no weird processes running. CPU temp lower than 11.4 or 11.3.1, as well.Somewhere in the depth of all the posts here there was this „clean installation„ recommendation. It is a fairy tail that one can survive several dozens or system software updates starting at 10.8 or before and end up in the very same state as doing a clean installation with the latest 11.4.
This has not been true with Solaris or Linux (had never a really compelling upgrade story) and it has never been true with macOS. Somewhere on the road you will always hit an unseen block and on the long run you waste more time with repairing than saved before by omitting the full backup, install, restore cycle. And doing the backup/restore cylce is always a good practise. You do not want to figure it out the first time in your life after a nasty hardware crash.
Yup. You should be able to check the seal with@dhinakg Okay, so I now gather that the deal with unauthenticated root0x800
is not so much that it automatically breaks incremental updates, as that it makes it too easy to break the seal on the OS, perhaps inadvertently, and then obv. you won't get an incremental update, at least not next update. Does that sound about right? (If so, that closes the issue - or rather resolves all my confusions, anyway - thanks!)
diskutil info
.I would bet a substantial chunk of money on the 2015-2017 Airs remaining supported. The firmware update analysis is clever, but that model is practically the most popular MacBook on university campuses to this day. I think even Apple would not risk the backlash from unsupporting it so quickly.Amid the speculation there is this: https://eclecticlight.co/2021/06/01/which-macs-will-be-officially-supported-by-macos-12/
Yes, should be ok.I would bet a substantial chunk of money on the 2015-2017 Airs remaining supported.
I'd doubt that, and I don't agree with the article on the cutoff for Intel Macs and OS 12. While looking at it from firmware updates is interesting, I choose to look at how Apple has traditionally handled what machines survive every summer. Usually anything that isn't a Mac Pro tower gets six years of OS support from when the machine was launched, give or take a year. Mac Pro towers usually gets 8 years.A very harsh cut-off if it eventuates would seem to suggest that Mac OS 12 could be the last Mac OS to run on Intel Macs.
Not going to happen. It is not in their pattern.if Mac OS 12 is the last Intel release
This is likely what would happen.I would like to see several more years of Mac OS updates for Intel Macs and a more gradual dropping of support.
That model is tagged as vintage now. So it might slip down into obsolete soon. It should get the macOS 12 but not beyond that, I would think.I would be disappointed if my mid-2014 rMBP didn’t get Mac OS 12.
Bonjour,Whose icon set and background? (Your own?!)
Thanks for that clear explanation @dhinakg (and @Bmju for pointing to it).This is because when the AppleInternal bit is set, the process involved in Big Sur OTAs switches to using an internal server (which has no DNS entry on public DNS), and since that server is not publicly available, it fails. (Redirecting it back to the normal server works fine.)
Nice mixe great jobBonjour,
Themes mixed from chris1111 (ModernFunnyBlue + Default-Dark-Low + don't remember sorry) for OpenCore 0.6.6, I redid the wallpaper (color and logo from OC, Apple and Ubuntu Mate) and redid my own icon for Ubuntu Mate.
And of course added the missing icons for the last OpenCore version. 😅