EOS is about return on time. I can install and configure Arch. For most of the machines I install, I would rather just use EOS since I like most of its defaults ( including Dracut ). Some of the EOS utilities are nice as well.
As you say, EOS is basically Arch once installed. So what is the downside?
Just having to hunt down and install yay on Arch is reason enough to use EOS to begin with.
I notice that CachyOS installs both yay and paru out-of-the-box. Nice.
I just did this last night. I put the Cachy repo behind EOS but ahead of Arch. That keeps the look and feel as EOS but grabs optimized Arch packages from Cachy.
If you are just adding Cachy repos to EOS, you have to install the Cachy kernel explicitly if you want it.
There are not that many Cachy packages actually. Almost everything still comes from the Arch repos. The ones Cachy replaces make sense if you are expecting to juice performance ( including some NViDIA patches in the graphics stack ).
I am also an EOS fan but I just took one machine and added the Cachy repos to it. Like EOS, it looks like it mostly just uses the Arch repos although, unlike EOS, I guess they offer optimized versions of some packages.
So, the repo hierarchy I have now is EOS, then Cachy, then Arch.
The repo install added a new keyring and upgraded pacman itself.
After a pacman -Syu, all it did was update binutils, Python, neofetch, zstd, kwin, and Xorg-Xwayland.
Neofetch still reports EOS.
I have not installed the Cachy kernel yet or tried their Firefox fork.
It seems like a fairly painless addition. Time will tell.
I have heard of Nala before but have never actually taken the time to install it. Based on your comment, I just checked it out on one of the Debian 12 systems I run. Turns out it was right in the repos.
Wow. So good. I cannot believe it took me this long. Jealous of it on the Arch installs now.
I installed it on Ubuntu 22.04 as well but it was not there when I searched. I had to add the jammy-backports repo first.
Thank you for the push.
When Debian 12 becomes Debian 13. It says in the article.
Just do it on ARM or RISC-V. RISC architecture changes everything.
Technically there are initialisms which cannot be pronounced ( letters only ) and acronyms which can be pronounced ( form words ).
So, in general, your rule is a good one. Of course, that does nothing to solve the problem of HOW to pronounce the words when so many different origin cultures are at play. As other have said, SUSE is German. So, is following “English grammatical rules” the right take?
I do not really have an answer. It is not self-evident to me. For Linux, Linus himself seems to have defaulted to US pronunciation. There is some precedent there I suppose.
Linux variation is simply because it was named after a Finnish person but became mainstream in parts of the world that pronounce those letters differently.
There are recordings from the early days where Linus clearly says “I say Linux as LEE-nuhks”. That is consistent with how you say his name in Finland. So, some people seize on that.
More recently, Linus has said that his name is pronounced differently in different languages but that “Linux is always lin-nuhks”.
Based on that, I thinks his latter guidance is correct. It is also basically the way most people in North America say it by default in my experience. This makes sense as Linus now lives in the US.
Ubuntu is an actual African ( Zulu ) word. It has a proper pronunciation.
It depends on your view of history.
The G comes from the GNU Project. While GNU is an acronym ( GNU is Not UNIX ), the accepted pronunciation is a hard G ( GUH-noo ).
When the GNOME project was started ( and named ), it too was an acronym where the G was GNU. So, it seems very reasonable to use a hard G.
GNOME is no longer affiliated with GNU and the project has stated that it is no longer an acronym although it is still capitalized. If the G is not GNU, it makes total sense to pronounce it as the mythical creature of the same name which is pronounced as a soft G.
I have not seen anything official on how to say it from the project itself. So, it may be a matter of personal preference at this point.
I use a hard G because that certainly WAS the proper name and I have not seen anything official saying they wanted to change it. They have kept the capitalization.
Remarkably close actually
Well, this is better news than him being completely gone from driver dev which has been the situation for months now. He formally resigned.
Of course, this may have already been in the works and the reason he left to begin with. Either way, good to see him back.
Things seems about to be in a pretty good spot NVIDIA wise. I do not use any of their recent gear so I do not care directly. That said, it will be good to have NVIDIA working well with Wayland just to remove the substantial amount of noise NVIDIA issues add to that project.
I installed CachyOS on a VM ( Proxmox ) just to check out the OOTB experience and I am glad I did.
In a lot of ways, it is similar to EOS as you say. That is a compliment as I really like EOS.
The UX is a bit different though. Lots more blue than purple of course. On the command-line side the differences are bigger. It uses the fish shell with a jazzed up prompt ( reminded me of Garuda ). There are a tonne of aliases. They clearly like Rust as a few of the Rust core util alternatives are installed. They even alias ls to eza.
Both yay and paru are installed at install which is awesome.
The default file system was XFS. Btrfs and zfs were both options. No bcachefs at install but it is available after.