zea

Linux has that issue too. A process in an uninterruptible blocking syscall stays until that syscall finishes, which can be never if something weird’s going on.

KDE can murder windows instantly (you have to set a shortcut), or you can also just send SIGKILL to the process

Parts of it seem to be inherently more secure, but there are some pretty glaring holes. At least software distribution is much more secure than the Windows approach.

If it was on something like BTRFS it’d probably be fine, though I imagine there’s still a small window where the FS could flush while the file is being written. renameat2 has the EXCHANGE flag to atomically switch 2 files, so if arch maintainers want to fix it they could do

1. Write to temporary file
2. Fsync temporary file
3. Renameat2 EXCHANGE temporary and target
4. Fsync directory (optional, since a background flush would still be atomic, just might take some time)