yxc999

Same here, I got a Gen 1 X13 for 120€, it’s not powerful by any means but perfect for running Linux and browsing, coding, writing and so on.

Yeah I get you, recently with everyone vibe-coding their stuff, there have been a lot of useless distros, but I really feel like I’m onto something useful. I’m self employed and basically temporarily took on less orders so I can work on this full-time until I get the first version out and actual full on development turns into maintaining and improving. I can definitely manage it and actually look forward to it as it’s super fun to me! Also I used today to make some changes as you can read in the comment I just left.

Fuck no

HiroshimaOS

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!

I took your suggestion to heart and decided to say fuck it and move my whole GitHub over to Codeberg. The non-profit nature, being hosted in Germany where I’m also from and ditching the last Microslop service I have make this something I should have done sooner. The only thing left is the repo for the website itself, I’m gonna set up the actions to automatically sync it with Hetzner tomorrow, I’m done for today!

Plutonium-239 - Arch Linux made unbreakable and lightning fast. Initial in-development release, announced here on Lemmy first. 19 days ago I announced my plans here on Lemmy and after four weeks and ~300 hours in total, I can finally share the first ISO of my project with this community. “sometime next week” yeah that was optimistic lmao I want to thank you again for the feedback on the initial announcement and I can say I tried my best to address and implement a lot of your suggestions! For the people that haven’t read the last post, this is the basic gist of it: Unlike immutable distributions that lock you out of the native package manager and force you into sandboxes, Plutonium-239 keeps the core Arch experience intact. You still get the bleeding-edge Arch repositories and the power of the AUR but all of that with a 5-20% performance boost from a heavily optimized kernel and the peace of mind of an unbreakable safety net underneath. For the ISO and the in-depth technical documentation, please visit my website at the link in the title! The 0.0.1 version is a pre-release/in-development version meant for experienced people interested in this project. I tested it extensively and I’m running it for a few days now on my Thinkpad myself, however I can IN NO WAY guarantee that this is 100% viable to daily-drive just yet. I’m very thankful for every person that considers testing this distro in a VM or on a secondary PC to contribute to the development of this project. Any feedback is appreciated and I hope my work can be of value to you!

I took your suggestion to heart and decided to say fuck it and move my whole GitHub over to Codeberg. The non-profit nature, being hosted in Germany where I’m also from and ditching the last Microslop service I have make this something I should have done sooner. The only thing left is the repo for the website itself, I’m gonna set up the actions to automatically sync it with Hetzner tomorrow, I’m done for today!

Thank you! Yeah, especially at the start you are bound to make a few errors but after a while it becomes smooth sailing. Regarding the burnout, I have autism and if it interests me and I use it for myself I will likely never burn out from it, I’ve put about 100 hours into this the last 12 days and I hate going to bed today instead of testing more on my ThinkPad haha

Very simple reason: you won’t even notice that something broke since the distro will fall back onto the previous version automatically

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!

Mal sehen, GitHub war das letzte Big Tech, bzw. USA-basierte was ich genutzt habe und war mir deswegen schon seit langem ein Dorn im Auge, bisher habe ich aber nie die Nerven gehabt zu wechseln. Jetzt war aber der beste Zeitpunkt, da das Hauptrepo noch leer war und ich meine restlichen Projekte aussortiert habe. Die kompilierten Pakete und ISOs kommen eh alle auf meinen Hetzner Webserver, Codeberg hätte quasi “nur” den Source-Code, sollte also verträglich genug sein und GitHub einfach komplett zurückzulassen!

Nice to hear! It might be the case that you will have to do some tinkering at first, but I would really appreciate any info I can get so I can get this to be stable as fast as possible!

Honestly, I haven’t even thought about that yet. I don’t see anything speaking against using other init systems at first glance, but that’s gonna be very low on my future priorities rn. If I should have some spare time after checking every mayor box then sure, I don’t mind systemd but I’m also not a huge fan.

I actually got it for 1249€ the same month it released! I’m super happy with it, worth every penny.

Yeah, I think I’m sold on it. This will push the 0.0.1 release back a day or so, but I want to ship a good product after all. Thank you all for the advice!

Silently working around a problem is how you end up with a system no longer set up the way you think it is. It’'s not working around the issue, it’s just refusing to update. You shouldn’t need to manually rollback a system that doesn’t boot. And you shouldn’t need to manually troubleshoot or fix it either. Just report the failing update and wait for it to be fixed. Jup, I think that explains my point perfectly, thank you! The point of most atomic distros is that it’s set up for you. If you want to manually investigate around and work around the issue yourself, then an atomic distro is probably not for you. I’d add to this that my distro will just spare you the time to unfuck your system. What you do about the fact that the update failed is still up to you to figure out, but at least you start the figuring out process in your damn DE. That in no way is “silently changing how your system works”, that’s literally just saving you time by doing something that you would have to manually do yourself if it was even a possibility.

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

That’s nice to hear! My personal feedback and the feedback from people that have tried it so far seems way better than I anticipated, noone seems to have any big issues. A little more choice during the install, a little less weird messages during updates (nothing critical, just looks odd) and some AUR packages that don’t install in a way that conform to the Arch guidelines (which is more on them than on the OS) and that’s about all the negatives. I’ll be on vacation for a week and only take my underpowered Thinkpad with me so I’ll be working on some little qol changes here and there to bring a more polished version in a few short weeks. If noone finds anything big that needs fixing I might even be able to justify bumping the version number of the next release to 0.1.0 instead of 0.0.2 since it’s way more stable than I dared to expect.

Hell yeah, let me know how it goes!

No, you are pretty cool!

No offense taken, but I didn’t use btrfs snapshots in a minute and spent 200 hours in the last 18 days working on my distro with a little less than adequate sleep due to my ADHD keeping me awake, thinking about what to implement next. Please cut me some slack haha

There are a lot of benchmarks for the CachyOS kernel and it’s mostly single digit performance increases for “normal” tasks but a noticeably more snappy feeling. The mayor increases come in compiling or rendering workloads, there it can easily get into double digits. For example on my 270K, compiling this kernel takes 23 min. with the stock linux kernel, 20 minutes with the linux-cachyos kernel in -v3.

My plan is to have it on par, if not better than them. Currently I “only” (this is the biggest factor by far) provide the CachyOS kernel compiled by myself but I already differenciate myself by also compiling it for -v2 CPUs. All five microarchitectures have their dedicated repos up and working and I plan to ship all the packages that will boost speed by being compiled microarchitecture-specific. I’m already building the server needed for that so compiling them automatically will be possible even while I’m on vacation next week.

I was just about to go to bed so apologies for the short answer, I can elaborate tomorrow if you wish. The home folder, including your settings/configs will survive, there’s no difference in the way you organize files to a regular Arch install. The partitioning is preset and non-customizable (for now at least). So no need to worry, you simply install it with the hardcoded presets and use it like you would use your current install!

‘Oh come on!’ was my initial reaction, but I’ve read your website, and thought: ‘hey, that sounds nice!’ Haha, I know I know, yet another Arch-based distro in this economy, but I really feel like this does fill a gap, thank you for your interest! On the other hand, perhaps the distros like this are meant to be installed by someone skilled to then be used mostly unattended by a regular user. My aim is to make this both appealing for the normie who just wants to use it like “SteamOS but with CachyOS speed” and run Flatpaks on it AND for the more experienced user who wants all the benefits of Arch but with a little more peace of mind. how would you know what’s a working state, so you need to return to the previous one? As the website explains, it automatically falls back to the last working state if it doesn’t boot, but obviously it can’t detect if something is messed up but still booting like in your example. In that case you just reboot and manually select the last working state (wip but kinda working already) just like a BTRFS snapshot, BUT it only rolls back the system itself, NOT your files. A BTRFS snapshot will also roll back your documents or whatever so my system, when it’s stable and tested, will be superior in every way to BTRFS snapshots.

Just gonna shamelessly leave these two paragraphs out of the website of my own distro here.

Either pu-239-update for the gui or /var/lib/pu-239/packages.list manual! Hmm, I’m undecided. Me personally, I couldn’t handle running a forum due to my autism, that would burn me out instantly. Having one entirely community run with me occasionally lurking in like I do here would probably be the only realistic option.

I don’t like black and white thinking and while I fucking hate LLMs in general, as 95% of times they are used for all the wrong reasons, I do have an Intel B70 for cases like these where current search engines just lead to nothing.

I have an X13 Gen 1 myself, which was the first machine (well apart from the probably 50 VMs I spun up during testing) to run this distro!

Yeah, it’s a shame that consumer hardware has gotten this expensive, but compared to the cost of other alternatives the B70 is a fantastic deal, especially at the old price. Cyberpunk 2077 still runs at 100fps at 3440x1440p with max settings RT off, Qwen3.8-27B at UD-Q6_K_XL with 131k context runs at up to 35tok/s TG and 900tok/s PP with my llama.cpp-sycl AUR package.

Well, it were four 80 hour weeks and I “only” reverse-engineered the way Fedora makes their distro atomic with ostree but adapted to Arch. I did try to stay true to the Arch philosophy of keeping it minimal otherwise so it wasn’t that big of a project!

Yes, it does come preinstalled with KDE as implementing a proper desktop selection is planned but would take even more time. This is Arch however, you can uninstall everything you want. Throw KDE out and install whatever desktop enviornment you want, you still keep the kernel and the ostree update model, that’s what’s so cool about it!

In a perfect world I would have loved to name it “Arch Atomic”, but I’m not affiliated with them so I went for a wordplay on atomic with my favorite isotope!

Lots of people with Thinkpads, I respect it haha. Yes, code can be contributed via Codeberg, donations via Liberapay, both are greatly apprechiated! Both links are on the website, but I’ll put them here for your convenience: codeberg.org/cantosun/pu-239 liberapay.com/Pu-239/donate

Yeah, you are right, I’m not the best at explaining things, I’m sorry. I look at it like literally Arch but the updates are atomic. You can choose to install or uninstall whatever you want, but it gets written with an A/B system during updates so you can always have a fallback. It does come preconfigured from the start, because that was easier to develop for now, but you can treat this like any other Arch install, just with safer updates.

True, if you set it up out of the box with CachyOS it rolls the entire disk back, but I forgot that option was a thing, my bad!

I still don’t get why I can’t opt in to participate in the survey every month, I’ve only been asked twice in the last three years on Arch

Nice comprehensive overview of why this piece of slop called a “distro” and its backers should be boycotted, thank you! Gives me even more motivation to finish up mine today.

That’s planned! Initially I actually planned to have a desktop selection in Calamares with KDE Plasma, GNOME and no DE, but while I was drafting the package lists for that I decided to push that back for a later release. This first one is more or less supposed to be a proof of concept so features like that are definitely in the works, but deemed overkill for the first version.

You are right, I thought about that too late, but if you search it together with “linux” it already shows up!

Yeah, Linux distros using something like Discord always seemed very odd to me. I mean okay, if you cater to gamers then I guess it makes sense, but you won’t catch me doing that. Lemmy is the only social media I have anymore, the rest is just braindead and bot-infested.

I’m excited to hear your feedback! Keep in mind, some things might be buggy, but please notify me and they will be taken care of.

Thank you! I was wondering why noone has tried that yet and now I know why, but hey, it works now. I hope you will have fun with it!

I’m making my own distro rn, announced it a week ago here and will likely release today or tomorrow! pu-239.org lemmy.ml/post/52307735

Interesting, thank you for that link! I was also thinking about bootc as a candidate but that seemed unintuitive to me so I went with ostree for now. The current implementation needs some refining but definitely is a better start that I imagined, quite happy how it turned out. Regarding the quotes, I’m brainstorming if there’s a way to, I wanna say “re-route” the pacman commands to edit the package list so you use the pacman commands like usual but they get applied as if you use the gui. It’s definitely possible but I’m thinking about how to get that to actually work in a clean way.

I appreciate it! I’d be especially interested in knowing if there are any locations/directories that the user expects to be carried through deployments or to be writeable that get deleted/overwritten during updates or are read-only in the first place. Finding that would perhaps also fix the issues with some AUR packages not wanting to install. Ideally you can e-mail me your findings to the address on my Codeberg profile and I could write on the code during the vacation and actually test in a VM on my main PC once I get back. Regarding the platform to discuss on, someone else asked a similar thing today so I’m just pasting my reply here “Hmm, I’m undecided. Me personally, I couldn’t handle running a forum due to my autism, that would burn me out instantly. Having one entirely community run with me occasionally lurking in like I do here would probably be the only realistic option.”

Haha, I feel honored to hear that! It’s still rough around the edges, but I already use it on my Thinkpad and the only issue I myself encountered so far is that I had to use vscodium-electron-bin instead of vscodium-bin since it wanted to make a systemlink that caused the install to interrupt, otherwise it’s been smooth sailing so far.

To put it in simple terms: when you update your system, it will be divided into two deployments. One deployment stays exactly the same, the copy will be updated. Until you restart you stay on the original. When you restart, the system automatically attempts to boot the updated copy. If it fails, it automatically loads the original again. That way the updates are atomic in the sense that you either boot into a fully updated system or simply back into the untouched original, nothing in between.

Yeah, you have a point, but still, twice in three years? I don’t know how representative it really is, ESPECIALLY when you see 50-100% ups and downs in the Linux user base. 5 to 3 percent and back cannot be the actual stat, that has to be unreliable selection of users.