Just run arch.
You should check the arch forum for any major breakages before you do. In practice most people don't check. You should read the pkgbuilds of aur packages though.
This is what Manjaro is supposed to do, but they don't actually test anything and it just breaks the AUR.
I played around with libreboot on an old Thinkpad once. Worked fine, but you lose access to the system setup BIOS screen. You may or may not care about that.
Thanks, I'll probably make the switch later this week. Is the new Cosmic ready or should I stick with KDE?
Last time I tried it was the first alpha and it definitely was not at that point. I think it's still in alpha as of now. I would stick with KDE personally. (you can of course swap it out later)
Like someone mentioned there are distros using different init systems. Gentoo in particular, you can choose to use systemd, or if you want you can run openrc. Technically I don't actually think swapping from one to the other after an install would be that crazy of a task. You would need to make sure you have all the tools needed for it to run. Change any files used by one, over to those used by a other. Etc.
Systemd is the most common one, and the one arch uses. Unless you know what you want, you want systemd, because most OOTB service configurations use it.
I have a w541 I librebooted. Which afaik might be the newest one that you can do it with.
It uses systemd and has ArchWiki articles on in-place switching of init systems, but in that case I think you're better off using Artix's variants if you don't want systemd.
I don't really trust myself to run a super duper custom solution so I'll just stick with systemd
He can't figure out how to search what init system arch uses. Very optimistic if you think he can read the handbook, or do basic troubleshooting stated in the wiki.
Nah the Gentoo handbook is fully nigger-proofed, even I can set it up without trouble
Correction, coreboot not libre. https://doc.coreboot.org/mainboard/51nb/x210.html
Ah yeah. Idk about that. I mean, the process will be similar in some ways. You will probably need extra work to make sure you configure everything for what you need. And to make sure stuff like the Intel me is neutralized if that is your goal. Since I haven't done coreboot itself I can't really say much about that.
Years of practice and patience. I've had the Lions Book recommended to me for a simpler to understand kernel ("A Commentary On The UNIX Operating System".) To a gorilla nigger like myself, all problems stay outside of the kernel space.
By switching to a different init system. As for why, my personal answer is that I'm not a paid professional working on Linux systems. It's just my desktop and I'd like for things to be dumb. This way, I can service the system myself and avoid having to depend on some retarded Internet freak so I can use their overly intricate tool. It's also a little contrarian in a way. The more software I see that straight up depends on systemd without a good reason beyond "just, like, install the social consensus program? Issue closed", the angrier I get.
Python sucks dick and now you know why. There are two Pythons, the legacy Python 2 and the contemporary Python 3. Some tools are also interpreter version specific because programmers like to neglect OS environments that aren't their own (see also why Docker exists.) Some distros, like Gentoo and Void, forcibly tard wrangle anything Python, to prevent this exact thing. The "easiest" way to install a Python program is to make a virtual environment for said program with something like its 'venv' module, install it there and make a shell script for executing that program through that virtual environment.
The latter is 90% of IT in general. You can escape the cycle of hell by using old tools and OS environments that just work. Not without some pain, because people really like trying to consolidate everything into one horrific glob, but it's very possible on Linux.
This is what I quite like about Nix (and to a lesser extent AppImages). Each installed package can have dependencies independent of everything else. Nix is the more elegant solution, it gets rid of the redundancies where dozens of packages each pull in the same library, but disk storage isn't sparse nowadays and AppImages just works better in practice.
Most software not infected by the modernism bug works fine outside Nix. Still, something less autistic might come along at some point and become the middle ground between regular package management and Nix.
Fedora has something like that with their rpm-os tree package management on their atomic desktop distributions. I tried it out long enough to start getting a hang of the general idea of how to use it. Then wiped it and installed a normal distro.
The whole dependency hell is not helping. As a gentoo user I cry every time I look at my crossdev build environments due to multiple packages requiring different versions of the same damn dependency (it gets worse cross ISA).