Powered by Arkdep from the Arkane Linux project this exciting new Manjaro variant is available for public testing right now! The goal of this release is to gather community feedback on the technology powering Manjaro Immutable. Note that this is only an experimental release and not representative of the final version, there is also no support guarantee, so hold off on installing it as your primary operating system, at least for now. We are hugely interested in gathering your feedback on Ma...
Immutables are cool—I’ve been running Silverblue for over half a year now. However, this seems half baked?
Unless I’ve misunderstood, you can no longer use pacman (without losing your changes after the next update).
And arkdep itself is just a shell script without any tests or continuous integration. I would be skeptical of using such a tool to control the integrity of my system.
it’s a manjaro project, ofc it’s half baked
It’s half baked: like the post says, it’s the first testing version. It will be developed more, like a member of the team said:
It’s clearly not ready.
It kinda feels like it goes against what Manjaro was supposed to be though. A safer version of Arch but with about the same features, including its massive software pool to pull from - and that exactly is what would fall flat in this case, since you’d need very selectively maintained “packages”, which would be extremely limited in comparison to someone with access to regular repos and the AUR.
I don’t know how Manjaro plans to do it, but Universal Blue distros have access to the entire set of
dnf
repositories, including non-free packages. You runrpm-ostree install
, and it layers the package you want. Each system update re-layers the custom package layer after upgrading the system layer.But since this is pre-alphaware, it’s kind of early to be passing judgement on how/if they’ll have access to the AUR and whether you could layer packages. Seems like the “safety” aspect is served through having an immutable system, which ensures end users have the same base as everyone else.
And it’s fine if that’s not your cup of tea. Sounds like it’s not. Arch, openSUSE, Debian, and their mutable descendants aren’t going anywhere.
I don’t know for the AUR, but the regular repos seem to be already accessible. You can try them with pacman, but the installed packages will be deleted at the moment of the update, or you can create a custom image and add the wanted packages which will be reinstalled at every update.
I don’t understand the hype of immutables, or usability even. I tried Bazzite today after Nobara nuked itself, and I couldn’t even paste my old Firefox profile since the actual folder apparently sits within the immutable folder structure. Maybe that’s fine for grandmas who just want to casually browse the internet but this seems extremely counter intuitive and an incredible hassle. I didn’t even have time to reach the software limitations with how fast I tried the next distro. Still hopping though, because apparently Fedora just nukes itself when you try to install codecs and I think I have about every major distro tested by now. Linux is cursed.
This is wrong. I run Bazzite and have transfered my FF profile over without issue. The Ublue “distros” just use the FF flatpak. You can follow the same instructions as you would on any other distro to move your FF profile with the flatpak version.
I haven’t had any problems with Bazzite, either, save for figuring out how to install Private Internet Access’s client, but that’s not immutable distros’ fault. The fault lies with PIA for not packaging their client in a sane way.
I couldn’t find jack shit, other than posts where people were saying that it sits within the immutable part of the distro and the profile manager just opened some temporary profile folder, with the permanent path being invalid / nonexistent. If that information is wrong then they should work at least on their documentation, which I checked for FF profiles and could find 0 entries.
Skill issue. I use NixOS btw. You can manage your dot files the immutable way as well if you develop the skills rather than yelling from your horse and buggy at the model T passing you.
Same reply that I wrote to the other entitled asshole: https://fedia.io/m/linux@programming.dev/t/1045299/Manjaro-Immutable-Out-Now-for-Community-Testing/comment/6595387#entry-comment-6595387
So you think immutable distros aren’t the future of Linux? I’ve got some bad news for you: This style of distribution is catching on like wildfire and IMO someday they’ll almost all be structured like this and you’ll actually have to learn how to work with it.
I’m not sure how what I said is entitled. I’m a REALLY mediocre programmer with limited time to learn and I STILL learned Nix and work comfortably with immutable distros.
SKILL ISSUE
If you make your distros even more unintuitive and a hassle than before, then no, it certainly won’t be the future. You people need a reality check.
It’s really not unintuitive, honestly. It is just very different than FHS.
“You people”?
If many things go from 1-2 steps to 20+ steps that I also have to read up on, but aren’t even documented anywhere which means I also have to be some sort of all knowing mystic (meaning they might as well be not possible to do), then yes, that’s very much unintuitive.
Maybe you “forward-thinking generation of software engineers that make elegant, reliable, declarative systems but are totally not entitled shitheads that insult everyone who clearly struggle with such elegancy” should actually listen to the issues that your potential user base is facing instead of dismissing them. Otherwise it will be hard to sell that “future” to them.
Thank you for perfectly playing your role of aging luddite principle Skinner who is stuck in the past and can’t (won’t) adapt to new paradigms.
I could probably summarize your experience as “skill issue”.
I suppose this article/blogpost by Lennart Poettering should suffice. Though, this article/blogpost by Colin Walters is also cool.
This is simply false as pointed out by others already.
You will have a very hard time on Linux with that mindset. And, to be honest, literally any OS you aren’t already familiar with.
I wouldn’t be surprised if you just searched this through your favorite search engine and settled with whatever random solution you came across instead of relying upon RPM Fusion’s documentation on the matter.
While this could be true, I wonder what prevented you from sticking with any one of them.
It’s definitely a lot harder if you’ve got major skill issues.
Blaming users for a lack of proper UX is always the best excuse.
Yet the only information I could find by other users of the distro. I even checked the official documentation, which contained 0 information on Firefox profiles. The FF profile manager only led to temporary folders and the absolute path led to an inexistent / invalid one (the one you’d expect them to go normally). So yes, I guess my skills are low, but so is the possibility for me to even learn anything when the only barely scrapped info I could find is wrong.
No, that and the rpm fusion install page is quite literally exactly what I used. Then no applications would launch, no UI functions would work and after I hard reset the PC it wouldn’t show me anything but a broken welcome page, which, when closed, left me with a blank black screen and my mouse cursor. I’m not sure what else you would expect me to do when following seemingly official command guidelines. But I guess it’s still my fault after all.
Let’s see…
Especially since absolutely no one is willing to help and rather throws insults and personal attacks around when facing people who struggle with all the major bugs.
I had a similar story, in fact EOS has a problem that they use dracut by default and is set to overwrite the kernel parameters every time you update the system lol.
I’m very sorry you had to deal with some users from here btw, specially the nixos people.
And people thought Arch users were stupidly entitled and toxic. My favorite part right now is him trying to repeatedly berate me for not being able to read out the correct profile folder within Firefox (which shows the default .mozilla/firefox/), even though I already mentioned that it does not show the actually correct one (.var/app/org.mozilla.firefox/.mozilla/firefox/). I guess he has “skill issues”.