The most common example I can think of is when you are compiling your kernel.. either you compile code into your kernel, or separately as modules which are then loaded at boot time (when the boot scripts run modprobe) after your kernel.
An example would be WLAN cards that supported N class when it was first available needed to have the module compiled and then loaded using modprobe as there wasn't support to compile them into kernel. Nowadays you are able to compile support into the kernel.
Main Topics
Browse All Topics
by: nociPosted on 2009-11-04 at 04:49:27ID: 25738732
Your system did the modprobe for you... ;-) at least if you have a modular system like most distro;s
Non modular nearly only makes sense for embedded environments with very thight single hardware setup.
It depends on the driver actualy...
nvidia distributes a blob on which an interface to the actual kernel has to be glued.
others have a binary only which might work or not.
To get closer to your example: https://www.openswan.org supplies an IPSEC stack.
If you get openswan it has a special tunnel driver available in source so that needs to be compiled.
If you get such a driver instructions NEED to be included in a README or other file on how to proceed.
There is no generic answer to your issue. But the openswan thing comes closest.
And indeed you need to trust your source of the modules code..., but even more if you can't verify the code.
With sources you can audit them or have them audited by a trusted party.