Sorry i don’t take advice from anyone who uses Edge browser…
8 Likes
Now, that’s good advice!
8 Likes
Generally speaking, production systems, or any systems that must be in working order, ought not to be based on a rolling-release system like Arch in the first place. (I don’t know exactly when the Plasma 6 packages became available in oft-used repositories for Ubuntu-based systems like apt - this is an important consideration.) Also, Arch-based systems are not suitable for Linux beginners (as I assume we all know), unless we’re talking about the Steam Deck or the like.
On a related note, I have had two bad experiences with dual-boot systems in which one OS is based on Ubuntu, and the other is based on Arch - particularly after updating via the apt repo in Ubuntu… so this doesn’t appear to be a viable solution. (To the best of my understanding, this has to do with the update to the GRUB configuration that is done on Ubuntu-based systems.) Fortunately, I managed to chroot my way back into the Arch system.
Edit: also, problems could occur with multiple DEs on the same partition, so this isn’t necessarily a safe option either.
Depends on the user. By updating weekly, bi-weekly, or monthly as opposed to every few hours or daily, you can limit the number of bugs you may experience while also keeping your system relatively up-to-date.
Facts. Which is another reason why Manjaro shouldn’t be considered as Arch-based because new-to-Linux users can certainly use it without issues if they don’t know anything about Arch and how things should be. ← Manjaro has nothing to do with this - just felt like taking a swipe at the distro. 
Not sure about the relevance here.
1 Like
I once had both EndeavourOS and Linux Mint installed on my laptop in a dual-boot configuration, in case EndeavourOS broke, given the nature of Arch-based distros. (Mint was a backup option at the time.) In the second instance, I booted into the Linux Mint partition, because I needed to locate a file stored in there. I performed a software update from there, not realizing that I wouldn’t be able to boot into EOS from the GRUB menu, subsequently. I wish I had known then that this would happen, but fortunately, I didn’t panic, and found a way to resolve this.
Most people on this forum probably know that Ubuntu and Arch-based distros don’t typically work well together (at least, without careful planning and configuring), but for the few who may not know, I hope this info proves valuable
Just for the record:
The issue with Ubuntu (-based) is that whenever the grub package is updated in the system, it tends to give its bootloader the first priority in the firmware settings.
A simple going to the firmware settings and change the priority back to the Arch’s bootloader will resolve the issue. No need for arch-chrooting, reinstallation of Grub etc.
Another option would be to disable efibootmgr in Ubuntu.
2 Likes
If I recall correctly, I think I did try that and ran into some initramfs issue, but I’m not sure
I would disagree I believe Arch is the best way to Learn Linux. By doing things by hand you learn to become more confident and more comfortable using Linux and the Linux tools. You learn the order of your system by building it. Its not that Arch isn’t for beginners Arch isn’t for those who want a silver platter handed to them. Arch is for those who desire Control of their system and who are not afraid of the OS.
5 Likes
Looks like their latest update went well, BUT a lot of them are more like this:
So I’m not sure I’d say that is quite as true as you make it out to be.
That doesn’t count all the users who can’t vote cause they can’t access their system 
5 Likes
I would say that it depends on the individual/user and situation. Most people who switch to Linux, I presume, do so after creating a partition separate from their Windows installation - in that particular scenario, one would probably prefer to play it safe. Many (if not most) people I know are tech-illiterate; yet we all rely on computers in some capacity. IMHO, I think it’s a great idea to learn to build a Linux-based system from the ground-up on a spare PC - preferably one that doesn’t contain any important files and folders.
I can confirm that I am currently learning Linux thanks to Arch (…well ok, thanks to endeavourOS 
)
…very slowly indeed, but I don’t think it has to do with the distro 
, quite the contrary actually.
1 Like
It kinda does prove my point, I think.
The fact that they have fewer issues is because they aren’t really a rolling release in the same way that most Arch-based distros are. They are more like Debian Sid or Siduction.
Your important files shouldn’t be on your PC anyway !
…and if it is the case, I would sleep so much better knowing those are only on a linux system than under a zindoz one
25% issues is proving your point? Ooof.
Debian SID is stated specifically by Debian it is NOT a production ready setup.
1 Like
sorry
Saying the same thing I already said.
Those are Windows Users
1 Like
Regarding why: The idea is: if you are a Manjaro user who knows how Arch works, then you know that you could be getting updates sooner and more frequently. This may cause you to add more up-to-date repos as your default, or even use the AUR. But this is a no-no on Manjaro, because you are likely to bork your system by doing so.
We’d actually need a poll here to do a “proper” comparison.
I also mentioned Siduction. And the point isn’t about whether it’s production-ready, it’s about the “up-to-dateness” of the repos.
And I’m sure they’re struggling to use Zindowz anyway, better do the same with a linux system
I update constantly and i rarely have issues.
Manjaro is Manjaro lets leave it at that. It doesn’t matter whether you think it should or shouldn’t be considered Arch-based. The fact is it is.
1 Like