Anonymous user
Modular Kernel: Difference between revisions
Jump to navigation
Jump to search
Added advantages and disadvantages
| [unchecked revision] | [unchecked revision] |
(Categorisation, Removed PFR) |
(Added advantages and disadvantages) |
||
Line 8:
The basic goal remains however the same: keep what is loaded at boot-time minimal while still allowing the kernel to perform more complex functions. The basics of modular kernel are very close to what we find in implementation of ''plugins'' in applications or ''dynamic libraries'' in general.
==What are some advantages and disadvantages for a Modular Kernel?==
===Advantages===
* The most obvious is that the kernel doesn't have to load everything at boot time. It can be expanded as needed. This can decrease boot time, as some drivers wont be loaded unless the hardware they run is used (NOTE: This boot time decrease can be negligible depending on what drivers are modules, how they're loaded, etc)
* The core kernel isn't as big
* If you need a new module, you don't have to recompile.
===Disadvantages===
* It may loose stability. If there is a module that does something bad, the kernel can crash, as modules should have full permissions.
* ...and therefore security is compromised. A module can do anything, so one could easily write an evil module to crash things (Some OS's only allow modules to be loaded by the root user).
* Coding can be more difficult, as the module cannot reference kernel procedures without Kernel Symbols.
==What does a Modular Kernel look like ?==
| |||