Do You Compile Your Own Kernel or Use The One Shipped With Your Distribution?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
View Poll Results: Do You Compile Your Own Kernel or Use The One Shipped With Your Distribution?
Like many others here, I used to compile my own. I would have to in order to make, say, my sound card or graphics work properly. I kept on compiling even after I didn't really have to any more, tweaking for (probably imaginary) performance improvements, or to just get rid of stuff I didn't need. At some point, the config process became ridiculously involved, and I quit. Nowadays, I use the default kernel provided with the distro. At most, if I feel I want a newer kernel than what my distro provides (and I'm running an Ubuntu-derived distro), I'll download binaries from http://kernel.ubuntu.com/~kernel-ppa/mainline/.
But nowadays, I don't find it necessary or particularly useful to 'roll my own'.
A dozen years ago, when I had odd things like a Tape Drive that was supported through the Floppy controller, or when I was running Linux on a 486 (for performance) it was worth it. Now, I just use the default. It has the extra advantage that with so much stuff in there by default, if you have to swap out a card or piece of hardware, you're likely to still boot. So, I used to compile (and it worked well, and at times gave a significant performance boost), now, it's better for me to just go with stock distribution.
Am using MX15 which is compiled by one of the expert MX packaging team. No need to compile my own kernel, but the option to change/update it is there if I wished.
I compile my own kernel by habit, to fine tune it and avoid a bunch of installed modules I will never use.
Also as I have efi hardware, I enable EFI stub support and Built-in kernel command line. This way I don't need a bootloader anymore.
Same here. I customize the kernel according to my ultrabook's hardware and the software I use (nothing special, though). Happy CRUX user.
I always use kernel that is sent to me with updates unless it fails. Then I just revert back to previous kernel by deleting it in the grub boot loader menu.
I used to roll my own a long time ago, with early versions of Slackware. Still using Slackware and also Linux Mint, but I haven't compiled a kernel in probably a decade now.
I use the kernel shipped with my distribution - Linux mint 17.3 Cinnamon.
Is there something in the shipped kernel that is very bad for the home user that has replaced Windows with Linux Mint?
I admin multiple machines with different configurations. Each one tailored to its specific needs.
One runs the shipped kernel, one runs the shipped kernel modified & recompiled, one runs mainline, etc.....
I used to compile my own kernel ions ago... using the ax25 protocol stack we had to in most cases. Now that the modules are in *most* kernels, it's nice to just kick it and call the modules when needed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.