Worth the trouble ?
Share your experience
Compiling your own kernel
Jaxson Torres
Chase Wilson
Want libre shit? Yes
Want meme schedulers and placebo memory optimizations? Yes
Want to save disk space on a computer with more than 16 megs of ROM? No
Noah Brown
It's not that hard, and it feels good, but that's about it, don't expect a difference in performance.
William Robinson
Not really.
Only when you need a specific tweak like RT_PREEMPT.
I copy /proc/config.gz, use menuconfig, set the local prefix (important!), build a full kernel with modules, setup the initrd, update grub, then watch it fail to find /dev/sdx.
build all sata drivers and ext4 into the kernel to skip initrd.
Ayden Ramirez
genkernel=justwerks
menuconfig=Compiled without error. Lets reboot!
Half a day later you realize you forgot to tick this IDE controller you didn't realize was on your motherboard.
Unless you know why you need to do it, there's no point.
You're going to do it though, so make sure you know exactly what hardware you have. Make a backup of /boot while you're at it so you can revert if and when you mess up.
Colton Ortiz
Do it all the time. Takes a hour or two on a core duo for a new one.
Jason Howard
Which kernel are we talking about?
Lincoln Perez
HAHA LOL try that with raid2.
Brayden Robinson
What the fuck, I meant lvm2.
Mason Baker
I had to recompile a kernel in order for a device to be recognized. It would also be cool to learn how to make the loading of my OS more efficient so I would say yes. I would always recommend keeping the original kernel just in case you fuck up with the new compilation.