I’m really interested in trying out an immutable distro like Fedora Silverblue. And I get the concept that the base system is read only and you install software through flatpaks.
But how does this work in practice?

If I change a config file in /etc, will the changes survive a reboot?
How can I see or decide which parts of the system are immutable and which are not?
Can I install packages that aren’t available as flatpaks, like more obscure stuff or command line tools?
What about ppd files for printing, firmware, drivers, fonts, icon packs, etc.? Where and how do those get installed?
Also, is it possible to replace or remove packages that are within the immutable part of the system?

  • superkret@feddit.deOP
    1·
    1 year ago

    So I’ve read up a bit, and I’ve decided that Fedora Silverblue isn’t for me.
    It just isn’t…simple enough. Like, the base concept is nice. But for example Firefox is part of the immutable system, which really screams “userspace app” to me, not base system.
    Then the system doesn’t replace dnf with a different way of handling packages - it adds 3 more on top. So now I’ve got 4 ways of handling packages on my system (rpm and dnf inside toolbx, rpm-ostree and flatpaks).
    And I have to decide which I want to use for what.

    • Mininux@sh.itjust.works
      4·
      1 year ago

      For Firefox I replaced it with the flatpak version and hid the system version, I found that better

      As for chosing what to install where, i made simple rules

      • If it’s available as a flatpak, I use the flatpak
      • Otherwise if it is system related/always required, rpm-ostree
      • Otherwise, I use distrobox (it’s like toolbx but better, it’s more integrated with the rest of the system and allows to have containers of other distros, for example I had some debian only packages and used an Arch container for AUR packages)

      But if it’s too much of a hassle for and it’s gonna be your daily system, yeah better not use it.