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.
You can build modules against kernel sources (no headers needed).
You can use symlinks pointing to your kernel image, since GRUB can read the filesystem (unlike LiLo) it will happily follow the symlink and load the kernel. So no, if using symlinks you do not need to update GRUB.
What reason would I need to build a module against the kernel?
For funtionality reasons for hardware maybe?
Well, if we are talking about kernel modules then building them against very kernel sources the module will be used with makes sense, doesn't it?
Yes, makes sense. I'll look online for an example where someone had to build a module against the kernel.
I've never done it-
The actual practice and seeing it done always helps me to understand.
I think the emphasis of the question was "why would I need to compile a module", more than "against the kernel".
In which case, yes, for new hardware is one possible answer.
Evo2.
Thank you!-
I'll look online where someone did that for new hardware.
I found a article with an example to help me understand how to compile a module.
I don't entirely understand it completly I'll continue to study this. http://www.cyberciti.biz/tips/compil...el-module.html
I'm kind of distanced from 'regular' Linux distros after I switched to Gentoo in 2003. In Gentoo all modules are built against kernel sources. Say, there is a driver which is not available in kernel. Examples from my household: r8168 NIC driver, VBox modules, nVidia kernel module. The only package in Gentoo that is built against headers (which is a separate package) is glibc.
I'm kind of distanced from 'regular' Linux distros after I switched to Gentoo in 2003. In Gentoo all modules are built against kernel sources. Say, there is a driver which is not available in kernel. Examples from my household: r8168 NIC driver, VBox modules, nVidia kernel module. The only package in Gentoo that is built against headers (which is a separate package) is glibc.
I don't see installing another version of the kernel on this "Voyager" distribution to be a good practice.
It would most likely be a waste of time.
I'd rather spend the time & effort reading more about the kernel and how to compile a module if I have to and continue
my reading the documentation on Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
