What is Silverblue?
fedoramagazine.org
What is Silverblue?
1–10 of 140 posts
Re: What is Silverblue?
#2Flatpaking all the things? I'm not sure why there is this push for Linux to have the "download and double click" install experience of windows / Mac. Convenient to install sure, but as a user its a nightmare to maintain/update.
All people on Linux really need is an xdg-open standard for opening a package manager / running an install command.
Re: What is Silverblue?
#3Flatpaking all the things? I'm not sure why there is this push for Linux to have the "download and double click" install experience of windows / Mac. Convenient to install sure, but as a user its a nightmare to maintain/update. All people on Linux really need is an xdg-open standard for opening a package manager / running an install command.
Are flatpaks not all sandboxed? I thought the concept of flatpak and snap was that it offered sandboxing in a way what was never implemented to normal repo packages
Re: What is Silverblue?
#4Flatpaking all the things? I'm not sure why there is this push for Linux to have the "download and double click" install experience of windows / Mac. Convenient to install sure, but as a user its a nightmare to maintain/update. All people on Linux really need is an xdg-open standard for opening a package manager / running an install command.
Are flatpaks not all sandboxed? I thought the concept of flatpak and snap was that it offered sandboxing in a way what was never implemented to normal repo packages
Flatpak uses kernel namespaces (like docker) to run software with a bundled set of libraries. From their FAQ:
> Flatpak mostly deployed as a convenient library bundling technology early on, with the sandboxing or containerization being phased in over time for most applications.
I don't really know if sandboxing is worth it for me. Running everything inside docker cotnaienrs sounds like an absolute nightmare when it comes to troubleshooting. You might think logs and things would be well defined and put in the right place for the OS to pick up, but if things were so well behaved we wouldn't feel the need for sandboxing now would we.
Re: What is Silverblue?
#5Flatpaking all the things? I'm not sure why there is this push for Linux to have the "download and double click" install experience of windows / Mac. Convenient to install sure, but as a user its a nightmare to maintain/update. All people on Linux really need is an xdg-open standard for opening a package manager / running an install command.
They are updated and maintained automatically, even if your distro isn't.
Re: What is Silverblue?
#6> The operating system is delivered in images that are created by utilizing the rpm-ostree project. The main benefits of the system are speed, security, atomic updates and immutability.
The article never mentions speed (or performance) again. Is the OS somehow expected to be faster because it is mounted read-only?
Re: What is Silverblue?
#7Earlier quoted context omitted.
Are flatpaks not all sandboxed? I thought the concept of flatpak and snap was that it offered sandboxing in a way what was never implemented to normal repo packages
Flatpak uses kernel namespaces (like docker) to run software with a bundled set of libraries. From their FAQ: > Flatpak mostly deployed as a convenient library bundling technology early on, with the sandboxing or containerization being phased in over time for most applications. I don't really know if sandboxing is worth it for me. Running everything inside docker cotnaienrs sounds like an absolute nightmare when it c…
I’ve been running many applications as flatpaks for over a year without issue. Troubleshooting is not too bad either imo.
Re: What is Silverblue?
#8Flatpaking all the things? I'm not sure why there is this push for Linux to have the "download and double click" install experience of windows / Mac. Convenient to install sure, but as a user its a nightmare to maintain/update. All people on Linux really need is an xdg-open standard for opening a package manager / running an install command.
They are updated and maintained automatically, even if your distro isn't.
Right up until they're not because they pegged the version of some library.
If things were so easily automatically updated and maintained we wouldn't need flatpak.
One benefit is that if you have some software in the chain blocking updates others can update.
This may actually improve overall security.
I think I just argued myself out of hating flatpak. :/
Which is cool, because that os-tree switching thing sounds like btrfs snapshot hopping on steroids.
Re: What is Silverblue?
#9As a Linux user from the 90s, I welcome this change. RPM Hell and its Debian equivalent are real and painful things. When disk space was a premium, system dynamic linking made sense. Today, it absolutely does not. rpm-ostree is a bit ugly. Snap has the right idea of doing both system services and apps. Fedora should do the same.
Re: What is Silverblue?
#10> The operating system is delivered in images that are created by utilizing the rpm-ostree project. The main benefits of the system are speed, security, atomic updates and immutability. The article never mentions speed (or performance) again. Is the OS somehow expected to be faster because it is mounted read-only?
No, I wouldn't expect this system to be faster in a meaningful way. Actually maybe a bit slower since fewer libraries will be cached / memory mapped between applications if they carry their own copies.