KDE can murder windows instantly (you have to set a shortcut), or you can also just send SIGKILL to the process
she/they
KDE can murder windows instantly (you have to set a shortcut), or you can also just send SIGKILL to the process
How convoluted was it?
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.
Arch Linux is a good vision and a tab for the meds
Listening to employees when making decisions, what a concept! It’s a shame many places don’t do that.
Most packages are purely additive to to system. If GNOME is part of the base system, I don’t care because I can just not use it. For packages that are mutually exclusive, well, usually that’s the distro picking it for you anyway, but if you insist on changing them then OverlayFS lets you mask files in the base.
For something like Arch or Gentoo, the read-only partition approach absolutely won’t work, but I know Fedora’s been working on an OSTree immutable approach, so it’s still technically a mutable partition but it’s defined declaratively and is still easy to roll back.
Immutable partitions are amazing for reliability, then you can just OverlayFS your mutable state on top of it
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
I think my BIOS has a setting to skip that part
2s in firmware??? I’m used to at least 30s
Do you get two empty spaces next to your tower? For maintenance if the lower elements.
It’s called a tower PC for a reason
All human strings are finite…
Steam OS is completely open source except for the Steam client.
They do, I was joking. It’s not as funny to say the ecosystem is slowly trudging along.
Wayland compositors might implement it this century
Maybe there’s a signal handler or some other outside force that knows where that variable lives on the stack (maybe through DWARF) and can pause your program to modify it asynchronously. Very niche. More practical is purely to inhibit certain compiler optimizations.
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.