Listening to employees when making decisions, what a concept! It’s a shame many places don’t do that.
she/they
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
You’re right, feelings do matter, and this post did not dispute that. It’s just that safety matters more.
It saddens me that the default interpretation of this is accusatory and requiring of defense. Not to personally blame you, this is very common and clearly a systemic reaction, but I don’t know enough psychology/politics/sociology to understand why, just enough to know it’s bad.
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.
It makes more sense if you think of const
as “read-only”. Volatile just means the compiler can’t make the assumption that the compiler is the only thing that can modify the variable. A const volatile
variable can return different results when read different times.
Can a EULA ban fair use? Google v Oracle might have something to say about this.
Arch Linux is a good vision and a tab for the meds