• taanegl@beehaw.org
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    They aren’t meant to be “flexible”. Immutable means it’s static, read only. You replace one image with another.

    In the case of Silverblue you install using overlays, like Flatpak or toolbox/podman.

    With NixOS you do get images, but in the form of clojures. BUT it also handles environments on a fundamental level, so you don’t need to reboot to install new system applications or services.

    Have you considered Vanilla OS? There’s also uBlue, but I have hopes for Vanilla because it is user-firsf distro, whereas uBlue is more an off-shoot of Silverblue meant for users, but Ruth and same issues as with Silverblue.

    Vanilla 2.0 is coming up soon and it seems like a great alternative for people with little to no know-how, or people who don’t want to mess around and find out.

    • Chewy@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Immutable can be flexible, just like NixOS is with nix shell and other features I don’t yet know about.

      Containers are great but rootless has issues with programs that need capabilties like CAP_NET_RAW, so I also need rootful containers. That’s annoying and is an advantage with nix shell.

      I’m not a fan of A/B root, which I believe VanillaOS uses. Also an advantage of NixOS is it’s big repo… On Fedora I had to package some programs myself in copr (tried out a less well-known wayland compositor) On NixOS I had to too, but it’s far simpler without the need to build on someone else’s infrastructure.

      • taanegl@beehaw.org
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Can be, as in NixOS is pretty much the only one, which I already alluded to.

        But despite you and me, some average users would benifit from immutable systems, even A/B root.