5·
2 years agoSilverblue and other distros like it fix this by not changing the running system. The pending update just becomes the running system on next boot.
- 0 Posts
- 8 Comments
Joined 3 years ago
Cake day: August 21st, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
22·2 years agoIt 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.
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…
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?
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.