HiroshimaOS

Very interesting, I’ll take a deeper look at that tomorrow, thank you!

Fuck no

Check out the comment I just left, I implemented a solution that pacman is now completely usable so it’s literally just vanilla Arch but atomic instead of being Flatpak-only!

Check out the comment I just left, I implemented a solution that pacman is now completely usable so it’s literally just vanilla Arch but atomic instead of being Flatpak-only!

Check out the comment I just left, I implemented a solution that pacman is now completely usable so it’s literally just vanilla Arch but atomic instead of being Flatpak-only!

UPDATE

I took your suggestions to heart and updated the website to reflect the changes I implemented today. The big change is that I found a way to keep pacman fully intact and functioning, but make it apply the changes atomically. So now this isn’t just limited to Flatpaks, but LITERALLY Arch Linux but made atomic.

The new intro reads:

“Plutonium-239 is Arch Linux, made atomic. It combines the rolling release model of Arch Linux with an atomically updated root filesystem inspired by SteamOS on top of the heavily optimized CachyOS performance kernel. Unlike immutable distributions that lock you out of the native package manager and force you into sandboxes, Pu-239 keeps the core Arch experience intact. You still get the full power of pacman and the official Arch repositories, with the peace of mind of an unbreakable safety net underneath.”

For more information, please check out the updated “How it works” section. Thank you all a lot for the feedback!

Thank you a lot for your interest! So as I pointed out in the other comments, out of the box and for the 0.0.1 release it’s intended to keep the system itself atomically updated through pacman and the user is advised to use flatpaks to install his applications. This is the most user friendly way of going about it, however I’m absolutely on your side and wouldn’t use it that way myself. 0.0.2 will have a way to “unlock” it so you can use the distro like vanilla Arch BUT you get peace of mind from knowing that you have a failsafe way of knowing the system will not break.

For the name, I did want Arch-Atomic at first but noticed this would violate the Arch Linux trademark policy and just went with my favorite isotope as a placeholder that unfortunately grew onto me. I will get off the couch now and edit the website so it’s apparent that Pu-239 is just the shorthand and people will refer to it as Plutonium-239 or just plain Plutonium in the future!

Haha, good thing to point out, however my plan is to make the second release able to be “unlocked” so you can pretty much treat it like vanilla Arch Linux but with a failsafe atomic way of the updates being applied. Being immutable is just the default configuration. Think of it more like Arch-Atomic but I couldn’t choose that name due to their trademark policy.

My initial idea was to just literally reverse-engineer the way SteamOS does it but when I saw what a mess this was I looked at a few other distros and how Fedora Silverblue used ostree seemed the most intuitive for me to program so yeah, that’s pretty much the reason haha. Are you just asking for clarification or do you think bootc has some advantages that you care to explain? Now would be the perfect time as the only machines running this are my ThinkPad, ThinkCentre and two friends on their spare laptops.

Honestly, for the packages I do agree. You are not going to notice if your damn font is compiled with v3 flags or not lmao. The kernels however do apply a meaningful improvement, even if it’s just in general desktop use, you DO notice the jump from 250Hz to 1000Hz. Currently I’ll just ship the regular linux-cachyos kernel with the EEVDF scheduler which is more general purpose, but if you select BORE for gaming or (I forgot the name) for throughput, it becomes even more apparent. I get almost a minute shaved off compiling the kernels when I use a good kernel!

The frontend isn’t even the goal, I won’t even be adding this at all unless it’s an often requested feature. Currently you can select KDE Plasma or Gnome during your install and both ship pretry much vanilla except for the distro’s logo and fastfetch. It’s intended to behave like SteamOS from a back-end perspective for lack of a better word!

Man if only that money would have been sent to them and not this clown.

Jup, there’s literally nothing going on from a design- or technical perspective. The guy pretty much just ships his Hyprland rice and calls it a distro. It’s just part money-laundering, part promotion of ideals.

First of, good on you to want to get deeper into it, you won’t regret it! Opinions have to be formed at some point or another, same goes for developing a sense for what sounds accurate or not. I do agree that Mint is easy and intuitive to use for most non-technical folk like idk, your parents maybe, and I do often recommend it myself, but visually? No similarity at all in the design-language in my opinion haha

What are you currently leaning towards?

I’m currently working on one, will release the website this weekend and the first public in-development build next week. I’m combining the kernels and CPU-specific optimizations from CachyOS (compiled and hosted myself to be in line with their repo policy and licenses) combined with the way SteamOS makes Arch-Linux atomic/immutable, implemented a little more to the way Fedora Silverblue does it. So pretty much unbreakable PLUS fast and optimized.

I will never get why Mint is regarded as looking similar to Windows, I guess it just became a thing for people to parrot (no offense to you, just complaining about why this is such a widely agreed on thing) when it only shares the layout but visually looks NOTHING like it. Very round, no gradients or transparency, just mono-colored, the design language has no similarity at all. Any vanilla KDE Plasma install looks instantly more recognizable to a Windows user.

Installing the Intel One Mono font, so much easier to read

💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯

haha yes