Related question: what is the difference between how an update happens in Silverblue vs uBlue?
For uBlue my understanding is that when you get an update you are downloading a whole image that contains the new version and then booting off of it when you restart. I think this is how chromeOS does it as well.
For Silverblue I thought it was the same, but I remember hearing somewhere that all that is touched are the parts of the OS that changed in the update. They’re being merged in with that git structure that ostree brings to the table, but you’re not downloading and booting off a new image with every update.
Am I understanding this correctly, or does Silverblue also boot off an entirely new image with each update?