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.
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: What kernel(s) do you use on your systems? Select all that apply!
generic
60
57.14%
huge
32
30.48%
custom build
32
30.48%
other
3
2.86%
Multiple Choice Poll. Voters: 105. You may not vote on this poll
Two types of kernel ship with Slackware -- "generic" and "huge". Most(?) users use "generic", some use "huge", while still others build their own. What's your preference and why?
This is another friendly, informal poll! Please do not take it too seriously, and please do not criticize other people's choices :-)
For ages I stuck with the generic kernel shipped with slackware, however on my new laptop the hardware is better supported on some of the more recent kernels. I've been building my own kernels from the linux-stable git tree using the config from slackware-current. It's pretty handy, whenever there is a new release I can just checkout the new git tag and rebuild.
What benefits do you guys get building your own instead of using the ones already compiled from a legit source?
Before Slackware 14.2 was released I had to compile my own kernel for hardware support, as the machine was quite new at the time. After that I was doing it so I could run grsec, but that patchset has since gone commercial (aimed at businesses, no small-timers).
I build my own kernel. For best support for my GPU I need a relatively modern kernel, right now that means 4.10 or newer. Additionally there are some other settings I tweak like latency.
I selected both huge and generic, but in reality, I almost always use huge for simplicity's sake. Right now, I only use generic on one system, and that is because I frequently adjust my harddrives, so I need to reference them by UUID. To do that, it requires and initrd, so I figured I might as well run the generic kernel.
I usually only build my own kernel if there's some new feature I need, but I think my last custom-built kernel was a 3.18 kernel when some new features (hardware assisted video playback decoding) were added for my old video card (ATI HD3870). Right now, I'm running a 4.9 kernel from -current on my frankenstein 14.1 system.
EDIT: Once I build my Ryzen system, I may keep more up-to-date with kernels for the additions/optimizations that will likely make it in future kernel series.
Last edited by bassmadrigal; 06-28-2017 at 08:27 AM.
On my Current test box with an older processor, I run the most recent HUGE 4.9.y because I am lazy
On my Slackware64 14.2 Work Laptop, I have been running the most recent HUGE linux-4.4.y, mostly because I am lazy, have plenty of RAM and it boots as fast or faster than GENERIC.
Now that I've committed to the intel-ucode.cpio file for my Intel 6700K, I may start running GENERIC since I need an initrd anyway ...
Haven't decided yet ...
-- kjh
Last edited by kjhambrick; 06-28-2017 at 08:48 AM.
Reason: System -> Work Laptop
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.