Hi there folks, I’m still learning about Linux and have yet to dip my toes properly in any arch based distro. Have for the moment fallen in love with the immutable distros based on Universal Blue project. However I do want to learn about what arch has to offer to and plan on installing default arch when I have time. But have been wondering why I haven’t heard of any immutable distros from arch based distros yet.

So, am left wondering if there are talks within that Arch community of building immutable distros?


While writing this post I found a project called Arkane Linux, which seem to be very interesting. Does anyone have nay experience with it? Is there a specific reason why immutable wouldn’t be a good idea when based on Arch?

Project: https://arkanelinux.org/

  • Sunny' 🌻@slrpnk.netOP
    link
    fedilink
    arrow-up
    3
    arrow-down
    2
    ·
    5 months ago

    Essentially: read-only system files.

    In immutable distros, you or any other programs that are installed on the system cannot modify the system files. That includes the system configuration files as well as applications. Its goal is to solve the problem of an entity gaining admin privlieges to your system and cause loads of damage. There are some addtional benefits too:

    • Updates apply at reboot
    • Root partition is read-only
    • Considered very secure
    • Sandboxed applications via flatpaks, snaps and appimages.
    • JackGreenEarth@lemm.ee
      link
      fedilink
      English
      arrow-up
      6
      ·
      5 months ago

      But then you also can’t make any changes to the system files. I thought the point of Linux was having more control

      • ddh@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        1
        ·
        5 months ago

        The entity gaining access to system files and doing damage, it’s me.

      • biribiri11@lemmy.ml
        link
        fedilink
        arrow-up
        6
        ·
        5 months ago

        Config files are still editable. Most of them (rpm-ostree, for example) have a mechanism for managing packages, and subsequently rolling back if anything goes wrong or completely resetting, and leave /usr/local writable. For stuff like development and working with compiler toolchains, you should be using a container. I use vscode exported in a distrobox running Fedora 40, for example.

      • Sunny' 🌻@slrpnk.netOP
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        5 months ago

        It all boils down to user preferences right. Some users prefer the maxium amount of control, while others, including myself, only use the pc for gaming and browsing, so I’d rather have a system that cannot be broken by myself and not deal with updates etc…