3 ms·
But there are also large differences. Silverblue still uses a single namespace for all libraries (unless you count Flatpaks, which can bring their own dependen
by danieldk 7y ago
But there are also large differences.
Silverblue still uses a single namespace for all libraries (unless you count Flatpaks, which can bring their own dependencies), whereas on NixOS you can have many different versions of the same library in parallel.
In NixOS, the whole system is defined declaratively, including the system configuration, whereas Silverblue uses a mutable /etc.
- edwintorok 7y agoAlso with NixOS you can install a package and start using it immediately, whereas with SilverBlue you first have to reboot the system to use the new package or after installing updates (or use one of the experimental live update features that tend to break booting the system). If you don't change the set of installed packages often, and reboot your system daily to get the updates, then SilverBlue works quite nicely. You can use containers (via podman or docker), and there is a builtin utility "toolbox" that gives you a persistent mutable container.
- vetinari 7y agoIn Silverblue, your /usr is really immutable, so when you install package, you are installing it into different tree than the one currently running. Reboot switches to that newly constructed tree.
- dorfsmay 7y agoIs there a dev version of silver Blue where you can install/remove package on the fly, and maybe commit and reboot once you're ready?
- snuxoll 7y ago`ostree admin unlock` will make the current image writable.
- edwintorok 7y agoYeah thats pretty useful for some quick hacking, it is all lost on a reboot though.
- snuxoll 7y agoThe —hotfix flag would remedy that. Honestly though it’s all fighting the design of the system, really there for developers to break things.