4 ms·
Actually, I was surprised to find that MacOS does a form of this, apparently - I recently attempted an update that failed and simply had to hold down ‘option’ o
by lostgame 8y ago
Actually, I was surprised to find that MacOS does a form of this, apparently - I recently attempted an update that failed and simply had to hold down ‘option’ on boot to select my regular drive instead of the update. The second time I tried the update it worked just fine.
- Wowfunhappy 8y agoI'm not 100% sure what you were experiencing, but this is not how macOS works under normal circumstances. Maybe while the update is in progress, but you can't just downgrade to High Sierra from Mojave so easily, once the installation is complete.
- Tsiklon 8y agoI suspect the GP saw this during a point release update on Mojave. Baseless speculation: I suspect that they were referring to Apple making use of the ability to spin up a new temporary APFS volume to store the Update packages + Staging environment and blessing it for boot. It makes a certain amount of sense to push out a static staging environment to then run the requisite OS updates and firmware updates from that controlled environment. That way you can reboot as many times as is required for the updates in the point release and still come back to the staging environment ready to go to the next stage - only needing to touch the User Data Volume when absolutely necessary. While not nearly as 'clean' as an atomic update on a read only root filesystem, this method could be significantly more controllable and more 'clean' than doing it live on the User's Data Volume. I suspect with iOS Software updates - it's a transactional atomic update as those machines all use read only root filesystems regardless.