It’s not really a big deal, but I am currently writing this using a linux kernel I compiled from source, which certainly feels like an accomplishment. The Arch Wiki has made the process fairly easy to follow. I just took the stock Arch Linux configuration without changes for now.
The most important part of this is of course that I have the option to do that, to take the source code of this incredible project and build my own kernel binary.
Fun times. Always keep a fallback kernel installed. Even if you’re not compiling your own.
I had to learn what chroot is when I borked my own kernel compile and there wasn’t fallback.
I feel like compiling your own kernel officially makes you not a normie. So… Welcome to the club!
Can I ask what are your pc specs , and how long did it take? + do you have a degree in computer science or prior knowledge of compiling code?
It took roughly 10-15 minutes on a Ryzen 5800X with 32GB RAM. I have compiled other programs before, but none nearly as large and notable as the kernel. I am in fact very close to getting a computer science degree, but that is in no way required to be able to do this. If you are able to follow the wiki-page I linked, you can do it too.
Nice job! Now you begin the journey of refining and perfecting your kernel config over time, to suit you. A new world awaits.
It’s not the compiling that kernel is hard - ironically, it’s one of the easiest things in the whole ecosystem to compile, got great tooling. It’s breaking down the mental barrier of something that you thought would be hard, but turns out to be completely within your grasp. Great work, keep it up, and never be afraid to keep pushing onwards.
I didn’t dare try to recompile it myself until I saw someone do it in a Youtube video. Changing the config is literally an interactive menu with labelled options and buttons. And your distro almost certainly includes a copy of the settings it uses, so you can just change a few values and keep everything else the same.
