Sort of. In my experience with Windows it gets really annoying. They tell you there’s an update and that you have to restart. If you put it off for long enough and just hibernate your computer, Windows will eventually boot your computer even if it’s “off” to install the update.
With Bazzite and other atomic distros it’s more like it lets you know that there’s an update available for you, and that the next time you reboot you’ll get that update. I personally haven’t ever had it bug me to reboot, but maybe it does that eventually. I don’t know of any Linux distros that would have the nerve to boot your system when it’s off to install an update.
Also, if you don’t want that update, you can “pin” your current deployment and you don’t have to update. Next time you boot you can choose the “pinned” deployment rather than the new one. Normally you wouldn’t want to do that because you’d be missing out on security updates, but if you’ve heard that the newest drivers are unstable, you can definitely choose not to update – or at least not to boot into the updated version.
Also worth mentioning that there are always 2 boot entries, the newest one and the previous one. So, if the newest one does get installed and there’s some issue, you can reboot and choose the previous one. Theoretically you can also roll back to an earlier one from months ago, but I haven’t ever done that.
So like forced updates in Windows?
Sort of. In my experience with Windows it gets really annoying. They tell you there’s an update and that you have to restart. If you put it off for long enough and just hibernate your computer, Windows will eventually boot your computer even if it’s “off” to install the update.
With Bazzite and other atomic distros it’s more like it lets you know that there’s an update available for you, and that the next time you reboot you’ll get that update. I personally haven’t ever had it bug me to reboot, but maybe it does that eventually. I don’t know of any Linux distros that would have the nerve to boot your system when it’s off to install an update.
Also, if you don’t want that update, you can “pin” your current deployment and you don’t have to update. Next time you boot you can choose the “pinned” deployment rather than the new one. Normally you wouldn’t want to do that because you’d be missing out on security updates, but if you’ve heard that the newest drivers are unstable, you can definitely choose not to update – or at least not to boot into the updated version.
Also worth mentioning that there are always 2 boot entries, the newest one and the previous one. So, if the newest one does get installed and there’s some issue, you can reboot and choose the previous one. Theoretically you can also roll back to an earlier one from months ago, but I haven’t ever done that.