SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I've built a couple of custom kernels in the past just for the heck of it and curiosity.
IMHO, it isn't worth the nose bleeding frustration of getting it right for my specific box.
I run 12.2 w/kde - ext 3 on one box and 13.0 w/XFCE - ext 4 on the other box,, both stock kernels.
The 12.2 box is at the login screen in less than 30 seconds when I bother to reboot.
The 13 box is at the login screen in about 20 seconds.
Everything works fine on both boxes that I use or need.
With this type of performance in my case, the only reason I could see to build a custom kernel would be for "the prestige" of it.
If it was a space issue or possibly a hardware issue, you would then be able to justify a custom kernel.
Then again, curiosity can over rule all as well as personal preference.
Poll with history perhaps - I used to routinely compile my own kernel in the Slackware <3.5 days, but haven't bothered anymore. Faster hardware, greater laziness, both have increased over the years.
When I started out with Slackware, I used to religiously compile a new kernel with every new kernel release, minor and major versions. These days I really can't be bothered too much doing that. I have found that for most hardware the slackware kernel just works.
Although I might just do it at some point for shit and giggles and keep the knowledge up.
When I started out with Slackware, I used to religiously compile a new kernel with every new kernel release, minor and major versions. These days I really can't be bothered too much doing that. I have found that for most hardware the slackware kernel just works.
Gee I think someone just said that. Plus I'm getting older and sitting in this chair for hours just kills me.
The stock kernel takes a little longer to boot but hell, I never shut this thing off anyway. I AIN"T GREEN!
If you have to recompile your kernel yourself, there is something wrong with your distro.
Ancient days of that nonsense are long gone by.
With the exception of specific hardware requirements that may require functionality not compiled into the stock kernels of typical Linux distributions including Slackware. The stock kernels already support a lot of hardware, and there's always the HUGE kernel, but sometimes HUGE is too big, and generic lacks something.
Regarding performance: If you choose a pre-compiled kernel for your architecture, you should be fine. Several years ago (not sooo long ago) I experimented myself with compiling my kernels. I was surprised by the result. At that time I didn't see programs run that much faster, but the start time of Java apps and OpenOffice.org was significantly shorter. I never understood, why, as I had only compiled the kernel, and not Java or OOo....
But that was the only noticeable difference in performance in my environment.
If you have to recompile your kernel yourself, there is something wrong with your distro.
Ancient days of that nonsense are long gone by.
I always felt the other way round. If your distro doesn't give you the control and transparency to configure any part of your system ,specially kernel, then you should ditch that distro. Hand holding doesn't work for me.
I always felt the other way round. If your distro doesn't give you the control and transparency to configure any part of your system ,specially kernel, then you should ditch that distro. Hand holding doesn't work for me.
Exactly, and even with slackware's generic ie. v4l(webcams) wont work out of box w/o building your own.
If you have to recompile your kernel yourself, there is something wrong with your distro.
Ancient days of that nonsense are long gone by.
The hand holding distros are great for those who are either incapable or unwilling to do their updates themselves, but that doesn't mean that there's anything wrong with the slackware approach. It's just aimed at a different audience.
Doing your own manual updates has many advantages, but comes with a cost in associated effort and required knowledge. Slackware is for those of us who believe the advantages are worth the cost. Clearly, its not for you.
Anyway, back on topic... I compile my own kernels, but only to keep up with the latest security updates rather than any desire to 'tune'.
If you have to recompile your kernel yourself, there is something wrong with your distro.
Ancient days of that nonsense are long gone by.
I'm guessing this is a suggestion that the user should switch to Ubuntu ... right ?
Well, let me inform you that you do not have to compile a kernel if you don't want to, or don't care to, or don't have the time to. But people still do compile kernels, and doing so is not only not nonsense, but sometimes it's a very good idea.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.