LeFantome

Interesting to see the Clang stuff on there

Interesting to see the Clang attributes on there

Interesting to see the Clang attributes on there

Started with Soft Landing Systems (SLS). Pre-Slackware. Many hours downloading floppy disk images at school.

Moved to Red Hat (pre-Fedora and pre-RHEL) until I think 7.3 or so and then Mandrake. I did trial runs with many distros over time but none of them really stuck. Fedora for a release or two. Spent a few years on Manjaro for desktop and CentOS for server. Have been on Arch for many years now (or EndeavourOS). Never used Ubuntu really.

Moved to Proxmox for server. Although I never used Debian historically, quite a few of the containers I have on Proxmox now are Debian based as is Proxmox itself.

Lately, I have been using Chimera Linux for desktop though I have an Arch Distrobox on it so I guess I am a bit of a hybrid at this point.

Glad you are enjoying Arch. I agree, it is no longer hard to install.

Do you have an example of something in the Arch wiki that does not apply to EOS?

I mean, I guess most people self-installing Arch are not choosing Dracut (though you could and the Arch wiki covers it). I cannot really think of anything else though.

I use KDE with Chimera Linux which is only in beta. Rock solid.

There is a difference. vi vs emacs is about preference as is GNOME vs KDE. All can exist side by side and the fans can duke it out.

Wayland is replacing Xorg. It is not a choice between the two. It is a choice between the future or the past. That is a more bitter pill for those that choose the past.

X11 the protocol will be around for quite a while. Xwayland has no end date in sight. But the Xorg display server is going to be parked on the history shelf next to SystemV UNIX. You can still run UnixWare today but UnixWare vs Fedora (or RHEL) is not a real fight.

Wayland vs Xorg is not a fight either. Wayland is not just winning. It has already won.

Outside of Xwayland, nobody is going to invest in Xorg going forward. Most Linux desktop users have already moved to Wayland. It will be almost 100% by the end of the year. BSD and other POSIX operating systems will follow.

The BSD folks say that they will maintain Xorg themselves into the future. We will see. My guess is that it will increasingly be an option for legacy hardware only.

Arch users do not consider EOS as Arch but it absolutely is.

EndeavourOS uses the vanilla Arch kernels, the vanilla Arch repos, and the AUR. There are only a handful of packages in the EOS repos and the majority of them are theming or utils that are what you would use on Arch as well (like yay and paru). There are a few quality of life utils that are totally optional and most EOS users are probably not even aware of. Plus, I suppose, the EOS keyring and a couple of packages so that the distro identifies as EOS instead of Arch. Distro identification is the only thing that “overrrides” anything in the Arch repos.

I describe EOS as an opinionated Arch installer with sensible defaults. Once installed, it is just Arch.

It is trivial to revert EOS to vanilla Arch if you want to. I don’t think it even requires a reboot.

I have never had anything in Arch take months to fix. One tip I would have is to use both the latest kernel and an LTS. If something “breaks” with a kernel module, just boot into LTS and it is probably fine there. I also had an issue with WiFi for about a week but a quick reboot into LTS and I was good to go immediately. When I tried the latest kernel two weeks later, it had been fixed there. Something similar happened with my FaceTimeHD camera. Same solution.

My current Linux distro uses APK 3 as a package manager. Updates are already atomic without the downsides of an immutable distro.

There are situations where immutable distros make sense but, for my desktop, it feels like a lot of compromise for benefits that do not move the needle for my use case.

Security is also a focus of my distro. My desktop does mot run any server workloads. I mess with it and tinker but I already use Distrobox and a COW file system. And I run two kernels, one bleeding edge (day-to-day) and one LTS (recovery). Recovering from breakage is just not a headline issue.

I guess the other factor is that I have limited time. So, my “tinker” budget is already spent. Playing with immutable distros may change my mind about them but they are far enough down the list that it may be some time before I do.

Bootable containers are something I want to play with though.

Just recently repartitioned my MacBook:

1 GB for EFI (vfat)

2 GB for /boot (ext4)

11 GB for swap

224 GB for / (bcachefs)

Grub cannot load a kernel off bcachefs so I need ext4 to bridge the gap. Once the kernel is loaded, it has no problem using bcachefs as root.

This is a laptop. On a desktop that can handle more drives, I would split /home onto a drive of its own.

I agree with you. But there is Distrobox if you want to “bring your distro”