In short, the author's argument is:
- no method to roll back firmware updates
- the sealed system volume is huge and rollback capability would require keeping the whole old ~10GB around, which is a lot of wasted space
In short, the author's argument is:
- no method to roll back firmware updates
- the sealed system volume is huge and rollback capability would require keeping the whole old ~10GB around, which is a lot of wasted space
IIRC that's how Windows handles update rollbacks, by doing this. Though disk space tends to be much cheaper on Windows devices, on Apple devices you pay a premium for extra internal storage.
I know what you mean by this, but isn’t this the case everywhere? Or at least on comparable systems, e.g. tablets?
Depends on the build quality. /s
I'd be removing that snapshot as soon as possible after a successful update.
After the live CD years it became much easier to abandon the headaches and work with large signed images, but most OS vendors have had at least one pressure to continue with the hellscape of patch permutations and one way configuration adaptions.
This wouldn't be such a wasteful idea had they used file system snapshot differential block transfer a la ZFS send. All I can guess is that they either think their customers are so rich they must all live in places with gigabit internet available, or they just don't care and everyone suffers. Either way it's a massive waste of time, resources and energy, just not theirs.
That would have been so epic. They should do that in FreeBSD. Take the macOS idea of having a separate protected partition for the base system, and combine that with the support for ZFS in FreeBSD to use ZFS snapshots to update the FreeBSD base OS, instead of having to run freebsd-update which applies a bunch of patches
I moved to FreeBSD precisely because I wanted more control than Apple would give me (which is ever less of course).
And freebsd-update works well, it can even validate files so you can see which have been manually changed. This is perfect for me, it's not a hard lock to what the provider decides but more of a suggestion.
They resisted any kind of low data mode for a long time because their “vision” was unlimited, unmetered everything.
Which is a nice vision. But not the reality for now.
This reads like Microsoft’s ‘the old new thing’ where they make up excuses for choices made by Microsoft and here for Apple.
I presume the real reason is that Apple would say instead of preparing for the update to fail, it’s better to make sure it doesn’t fail in the first place.
On a PC laptop it often is. Even on many all in ones now.
Compare like for like for goodness sake
[0]: https://www.google.com/chromebook/discover/pdp-samsung-galax...
32GB eMMC, not enough to do a feature update. The Celeron and 4GB RAM were not ideal either.
I think it was a PC. The low end of PCs is amazingly awful.
Don’t know if you’ve looked at that segment but, maybe it’s not what you loop for, but it started not long after Apple did (HP & Dell’s MacBook Pro design-ripoff series especially)
Also many lower end laptops have done it for a looooong time.
s/even/especially/
This used to be unheard of on PC laptops. Soldered storage in PC laptops is a recent development (past 10 years or so)
But, yes. It’s a form factor thing really, as people want smaller, thinner, lighter, laptops. Memory (and battery) removability gets sacrificed as those aren’t a priority for most customers
What difference does that make? The old version just needs to be kept on disk, not in RAM.
But even if the backup has to be stored on the on-board SSD for some reason, so what? It's temporary. That storage can be reclaimed when it's needed. MacOS is already using on-board SSD behind the scenes for Time Machine backups when you don't have an external drive attached. I see absolutely no reason why it could not do the same for a rollback image.
The real reason you can't roll back is simply that Apple doesn't want to allow it, because that would make it easier for the market to reject one of their updates.
Bingo. OpenSUSE makes it easy using BTRFS snapshots, enabled by default. Apple and Microsoft could make it easy too but empowering users like this isn't in their interest.
Right. That's why your Time Machine backups stop worki--oh wait, their integrated backup software lets you restore your disk to the state before the update. So your narrative is FUD.
(It also puts the burden on the user to actually make a backup before upgrading.)
https://coingeek.com/five-years-later-apple-removes-bitcoin-...