Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
I have a question in mind, I did some research too but I can't see relevant answers. Here's the deal.
What is the difference of a generic and huge kernel? Well I set up my slackware with LVM partition and they said that change the kernel from huge to generic, now I'm curious about the difference of two.
A generic kernel typically has a small(ish) statically-linked core and a huge number of modules. There will be modules to drive every kind of hardware that the kernel supports, but only a few of those will actually be loaded. It's the job of the installer program to work out what modules are needed on a particular machine and create the appropriate files in /etc/modprobe.d.
I think the Slackware huge kernel has all the drivers on board so that it can handle any hardware out of the box. That's useful on an installation disc but rather clumsy for day-to-day working.
A generic kernel typically has a small(ish) statically-linked core and a huge number of modules. There will be modules to drive every kind of hardware that the kernel supports, but only a few of those will actually be loaded. It's the job of the installer program to work out what modules are needed on a particular machine and create the appropriate files in /etc/modprobe.d.
I think the Slackware huge kernel has all the drivers on board so that it can handle any hardware out of the box. That's useful on an installation disc but rather clumsy for day-to-day working.
Nice explanation, so using generic kernel is good for optimizing your system cause it will just load some of kernel modules needed. Am I right? Thanks.
Yes, it is better than the huge kernel - you can say, in general. But if you really want to optimize you will need to recompile the kernel for your own hardware (which will contain all the drivers you use - not as modules, but built-in).
Yes, it is better than the huge kernel - you can say, in general. But if you really want to optimize you will need to recompile the kernel for your own hardware (which will contain all the drivers you use - not as modules, but built-in).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.