Pu-239
pu-239.org
Pu-239 is an atomic Arch Linux distribution: sealed read-only root, ostree A/B deployments with automatic rollback, and the 1000 Hz linux-cachyos kernel.

As the title and the website say, I’m currently making a distro with the goal that you don’t have to compromise between ease of use + safety and bleeding-edge + performance optimizations.

As I will likely be able to publish the 0.0.1 source code to the GitHub link and the ISO to the website sometime next week, I would like people to be aware of my project so I can have some feedback for further improvements when I release the first version. I have not posted this anywhere else yet, as I value the opinion of this community more than Reddit or whatever.

If you have any questions or any criticism, please voice it, I would love to hear it, good or bad, in the end I want to make a proper OS. (I’ll go to bed now so expect replies to take a few hours from posting.)

  • Nibodhika@lemmy.world
    3·
    19 hours ago

    That’s an interesting idea, but if you make Arch’s root read only you’re leaving behind pacman/AUR (and to a good extent the Arch wiki) which are usually the main advantages of Arch based distros.

    SteamOS solves the stability issue by providing runtimes for games, I didn’t read anything there about anything similar on your distro. Correct me if I’m wrong, but it seems you’re not solving the stability issue, or in other words you will still be unstable as this will be a rolling release. In short I don’t see what would be the advantage of this over base Arch + Snapper (or timeshift).

    In that regard, how is this different from Bazzite? I know it will be a different kernel and package versions but in principle the philosophy seems to be exactly the same, and I don’t expect the kernel/packages to be that different either.

      • Nibodhika@lemmy.world
        3·
        12 hours ago

        Interesting, how are you dealing with pacnew/pacsave files? From your explanation it seems that they would go into the read only filesystem and would need to be resolved manually and preserved there until some old version cleanup is ran.

        And while I find the idea of a writable overlay filesystem for the /etc fascinating, I think that could have issues with some rollbacks and backwards incompatible config changes.

        At the end of the day seems like a fascinating project, but I wonder if Arch+snapper wouldn’t be better overall.