

Silverblue and other distros like it fix this by not changing the running system. The pending update just becomes the running system on next boot.
Silverblue and other distros like it fix this by not changing the running system. The pending update just becomes the running system on next boot.
It only works if you have an ARM CPU with an NPU.
No, it works on x86-64 assuming the device has a sufficient NPU. Both AMD and Intel CPUs latest CPUs list the Recall preview as available now.
They said every radio frequency not every electromagnetic frequency.
If they did, I’d imagine “jamming” gamma rays is going to have some side effects.
Most computers firmware can store a Windows executable. Microsoft pushed for an addition to the ACPI tables called WPBT. That stores a Windows exectuable in the firmware. It is of course totally used for the intended purpose…
The difference is that Proton wasn’t a thing the first time.
Nier Automata gets really meta…
If I were to speculate, they are waiting for the NVK (Open source NVIDIA driver) to be more mature. So, they wouldn’t have to release two versions and wouldn’t depend on NVIDIA to update their driver to work with software the Steam Deck uses. I.E. Steam Deck uses gamescope for everything outside of Desktop mode. NVIDIA’s driver didn’t work with it until 2 months after the Steam Deck release. Even though it had existed for years prior.
This doesn’t contain the game code either. It takes a user-supplied ROM and converts it to an executable. Nintendo do not own the code that performs the conversion.
IIRC main Fedora used to not do this until some update crashed people’s sessions including the update process which left their install in an unbootable state.
The ostree based versions like Silverblue avoid this by their updates not touching the running system and instead creating a new folder structure with the updates applied that will be booted into on next boot.
I just use the Firefox flatpak from flathub.
Definitely a strange choice for a distro that pushes flatpak to not use it for the browser by default.
Are you referring to the ones with excessive sandbox permissions that flathub allows by default? Or is this something else?
Since drivers are so specifc, people’s anecdotal experiences with having to install them is never going to be shared.
IE, I had to install a wired NIC driver just last month on a fresh Windows 10 22H2 for a Dell laptop that was no more than a few years old.
That isn’t entirely true. You can change it as long as it is done via package overrides or overlays. Sure it rules out just compiling/installing something into your root unless you package it first but you can change it.
I honestly like the fact that it effectively enforces every file in the immutable parts of the OS to be traceable back to some package.