Manjaro to EndeavourOS experiences

You can always invest in a bigger rug.

Anyway I’m glad it’s clean now, though that was a bit stressful for the poor thing. Maybe use prevention next time so it stays clean.

2 Likes

I found I was reliant on the hand-holding (of Manjaro) more than I realized. I feel like a newbie again. There is a bit more to kernel building than just curating the .config. I’m thankful that @anon31687413 posted his kernel PKGBUILD

6 Likes

Patience, you’re not allowed to have one til you reach TL3.

4 Likes

Why not edit your post and turn that into a link to the thread. :wink:

I’m happy with the frequent updates and nvidia 450x drivers, Manjaro is still using 440x. I also appreciate the few EndeavourOS tools such as the update notifier and the friendly way of updating mirrors. There is also a lot less pre-installed packages and software I will not use. I was using zsh on Manjaro and I still use it on EndeavourOS.

6 Likes

I still like Manjaro, even though I decided to stop using it and convert all my machines to EndeavourOS (and it could have been vanilla Arch, too, there’s little difference, which is one of the reasons I like Endeavour so much).

I genuinely think that Manjaro is the best distro currently in existence. It has most of the benefits of a pure Arch system, but also curated and well-maintained repos that make for a very low-maintenance, low-effort system. Sure, Manjaro’s default installations are a bit bloated, and contain “malware” like snapd, but it’s not at all difficult to debloat Manjaro (at least it’s easier than getting everything to work on a pure Arch system, especially on older or poorly supported hardware). I’ve been using Manjaro for about a year on all of my computers and it has been a really enjoyable experience.

The reason I decided to switch to EndeavourOS is the fact I don’t want to be dependent on the whims of the Manjaro Team, especially now that they decided to part ways with @jonathon, who was their loudest voice of reason whenever they made questionable or unpopular decisions (like with the "Free"Office debacle). This is not bashing Manjaro. I love Manjaro, I just lost confidence in the ability of its devs to make good long-term decisions. I dislike the direction of wannabe corporatism that the distro is heading towards: it is as if Manjaro GmbH is trying to out-Canonical Canonical. So, my decision to switch away from Manjaro is one that I perceive to bring me more long-term independence: it has nothing to do with the present quality of Manjaro, which I think is still very high.

22 Likes

Kinda sorta mostly ditto. I have zero regrets for my 3 years of MJ, & feel immensely grateful for its quality + the fab community, but… finally it became time

10 Likes

I too noticed that Manjaro did a lot on their ISO’s.

When I thought I finished my install script and converted my main system to EOS, I noticed I needed a few extra programs that I forgot to add like one for disk management and mass renaming and a few others.

Also needed to enable the cronie service myself so timeshift can make it’s backups and also had to enable the bluetooth service so my controller would connect.

Didn’t hated it though, just more stuff I got to learn about the workings of Arch Linux. I also learned that I can set my ENV variables in the .profile. I used to write them to /etc/environment but doing it in .profile is cleaner and maybe the correct way as well.

4 Likes

Technically, there wasn’t that much to do to convert Manjaro kernel PKGBUILD into one that’s compatible with Arch.

That PKGBUILD I posted is maybe not a good reference for starters though, it contains a little more than most AUR kernels, like e.g. support for building with Clang’s IAS, as well as module signing with custom keys.
Also retains Manjaro’s “extramodules” facility. It’s for curious nerds :wink:

6 Likes

me2

6 Likes

Same here. I am not anymore using Manjaro for the exact same reasons explained by @Kresimir and others here, but I am grateful to it as it allowed me to to leave Ubuntu in 2017, and to discover the Arch universe. I still would advice to try it to a newcomer to the rolling distro concept, and I still read the Manjaro forum, even if I am no more active there.
As for EOS, what can I say… I feel like being in love again.

12 Likes

I am still running both in my system. Manjaro is great Linux Os and so is EOS. I have been learning a lot and enjoying it, having big fun. I don’t think I could stop using both linux Oses for they fully provide the best for my personal use and linux learning.

5 Likes

Best thing ever happened to me as well! :slightly_smiling_face:

I use Arch, btw :laughing:

5 Likes

A fair and reasonable opinion.

3 Likes

I have no problems with Manjaro or the team.

But........

I am just stalking @jonathon:rofl:

15 Likes

Some aspects of kernel building is old hat for me. I’ve been hacking at debian compatible baytrail kernels for Ubuntu derivatives for years, but my all intel rigs didn’t need extramodules and make makes the .deb packages for me auto-magically. I’m not used to handling more of the details myself. :sweat_smile: With Manjaro, I was able to just tack on a couple more patches and wrestle with the .config to get a usable baytrail (mini-)kernel using their standard PKGBUILD, so I never studied the build details.

Now that I have a new AMD machine that needs some patches I haven’t found yet… I’ll look at some of the aur kernels, there’s probably an AMD kernel there already. I’m at my best cutting and pasting and step-wise refinement versus pioneering new trails…

2 Likes

https://aur.archlinux.org/packages/linux-amd

3 Likes

Same here. Oddly enough after migrating here, I don’t feel like I need as much hand holding. More of “Oh this is different, how does it work?”, then I’m off to the races configuring whatever.

I find it very refreshing with a blank slate OS and building it the way I use it.

6 Likes

How about…Linux from scratch?! :sweat_smile: :crazy_face: :penguin:

2 Likes

Not ready for that :rofl:

6 Likes