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.
You must log in or # to comment.
That we can make software unique to our needs is one of these best parts of software freedom. Good for you!
Maybe it’s not a big deal… But I still remember the first time I compiled the Linux kernel. It feels good. Well done!!
I often did this for years, using -march=corei7 and -mtune=skylake or whatever was the best option for my cpu, patching with brainfuck scheduler, etc.
Now I don’t care really 😑
It’s always cool to tinker with kernel and config, congrats 🎉
As a student I wasted so much time mucking around with flags and settings in Gentoo. It definitely wasn’t pointless since I learned so much, but I didn’t need to sit there and watch it compile as much as I did.
It was pleasing to watch though, just like defrag in Windows.
just like defrag in Windows
That felt more a horror for me.
Defrag all night and wake up to the sound of the hard drive failing.
Now that’s horror.
You have backups. Right. Right??
A friend of mine is a musician. About a decade or two ago I went over to his house and he said that he had to get a new fan to fix his computer. I asked him what was going on, so he turned it on and I heard that tick-tick-tick of the read head. I had to let him know it was his hard drive. He had a lot backed up, but not everything, and not the stuff he’d been working on the past couple weeks. Just a bummer. But he did set up a backup program after that.
ahh what a shame. I have: https://kernel.melroy.org/.
But I also didn’t had the time to create new kernels. My PC is too slow at the moment. hahaha. Just wait… maybe I will get the latest threadripper. Instead of the first -gen i7 from 2008.
This is the best part of free/libre/open-source software. Even if you would never want or need to compile software yourself, the fact that you have the option to do so, and the opportunity to learn how the software works, is what makes FLOSS superior to proprietary software IMO.
I just compiled Handbrake from source a few minutes ago, and I know how you feel. Best of luck in your future code-compiling endeavors.
Achievement unlocked… now try this… https://www.linuxfromscratch.org/lfs/
8MB for an entire thing running a web server.
Mind: blown
How long did it take to compile?
I didn’t really keep track, but I would estimate around 10-15 minutes on a Ryzen 5800X.
I compiled my first Linux kernel back in the mid 90s, mostly on 386 and Dec Alpha hardware, interesting enough both were not that much slower than what you mentioned, I think the alpha (a measly 21066) took about 40 minutes. If you had asked me back then, I’d probably have imagined a minute or two, 30 years later. Guess it says something about how much larger the Linux kernel has become.
That just brings me back to starting the compile, getting something to eat, doing chores, and whatever else. Then when it was finally done, booting it up only for it to not boot because I forgot some checkbox. Repeat a couple of times. Nights getting the thing working. And then on the next kernel release, trying to make sure I remembered all the checks because it didn’t let you export the current config back then.
Last time I compiled a kernel it was on a bus-overclocked K6-3/500 (higher bus, lower multiplier).
not OP but on my i7 7700K a fully-featured kernel takes about 2 hours or so to compile. if i minimize the kernel to only the modules i need i can get it down to 20-30 minutes (clean). incremental compiles barely hit 5-10 mins
overall not a big deal, especially compared to something like firefox (or god forbid chromium). or gcc with pgo (which is technically cheating because it compiles itself 3 times if you enable pgo)
Congratulations on being awesome. Keep that shit up.
you win one on these
https://www.jeffgeerling.com/sites/default/files/images/800.jpgCongrats!
Nice! After the first time you get the hang of it but keep in mind, If you do make your own config you will have to recompile your kernel for any hardware that isn’t automatically enabled in the config like graphics, touchpad, tablets, and other peripherals you will plug into your computer. Reading up on what hardware you have helps a lot but I still manage to forget something when I have to create my own config. Thankfully you can just transfer your config to the next kernel instead of creating it all over again.
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.
Yes, that was my experience as well. And of course there is the added tension that if you mess up somehow your system might become unbootable.
Nice! I also compiled the kernel multiple times when I used Gentoo back in mid 00’s. It may not be a big deal as such, but I feel kind of good being able to say I’ve done it.
Next challenge: write your own kernel.
I installed gentoo from stage 1 or maybe 2 back in the day… it compiles to compiler to compile the rest of the build process and then compiles the kernel and base… quite fascinating but it took about 3 hours on the hardware I was using.
Congrats! Keep this kind of mindset if you can, even later in life. It will continue to take you farther in life than you would imagine.
Yep. The mindset will take you much further than the kernel itself.
Surely this is a feat of engineering on Arch. But in NixOS, this is just Monday. 😉
I used to do this with Gentoo, and it was always a blast! Glad that you’re having fun “rolling your own!”
