This is a lot safer on Linux than Windows, this year. A lot of engineering has gone into making updates resilient.
And Linux hasn’t done the Windows 10 to Windows 11 - black screen for a couple hours, hope you know not to touch it - that we sometimes see.
Linux now has a stronger default permissions model, so it’s a lot harder for user error to break the machine in serious ways, even if they do reboot during a sensitive update.
Anything’s possible. But, they try to make that hard. The system always keeps 2 versions around, the newest one and the previous one, so if you screw up the newest one you can always boot into the previous one. And Bazzite, at least, uses BTRFS which uses copy-on-write, so it’s much harder to corrupt the filesystem. I think the /boot partition is still ext4 though, so it’s possible that if you time it just right you could theoretically mess up your boot partition. Then you’d need to use a rescue USB drive to fix it.
Until everything breaks because the average user held down the power button mid-update because the computer wouldn’t shut down.
This is a lot safer on Linux than Windows, this year. A lot of engineering has gone into making updates resilient.
And Linux hasn’t done the Windows 10 to Windows 11 - black screen for a couple hours, hope you know not to touch it - that we sometimes see.
Linux now has a stronger default permissions model, so it’s a lot harder for user error to break the machine in serious ways, even if they do reboot during a sensitive update.
Anything’s possible. But, they try to make that hard. The system always keeps 2 versions around, the newest one and the previous one, so if you screw up the newest one you can always boot into the previous one. And Bazzite, at least, uses BTRFS which uses copy-on-write, so it’s much harder to corrupt the filesystem. I think the /boot partition is still ext4 though, so it’s possible that if you time it just right you could theoretically mess up your boot partition. Then you’d need to use a rescue USB drive to fix it.