Difference between revisions of "Kernel Competence"
(→Introduction) |
|||
| Line 5: | Line 5: | ||
On this page and its sub-pages we will collect all information connect to the kernel, like managing kernel modules, retrieve information from the kernel and use special commands. | On this page and its sub-pages we will collect all information connect to the kernel, like managing kernel modules, retrieve information from the kernel and use special commands. | ||
| + | ==Kernel== | ||
| + | |||
| + | The kernel is the interface between the hardware and the software. The kernel lets the software write data to disk drives and to network. When a program needs memory, the kernel handles the access to the physical memory chip. When a program requests CPU time, the kernel organizes it. The kernel provides all the software interfaces that a program needs, in order to access hardware resources.<br/> | ||
| + | |||
| + | To follow the UNIX philosophy: to minimalist, modular software development the Ghost/FreeBSD kernel is set together out of modules. If a hardware requires a special piece of software, a appropriate module has to be loaded in to the working memory. Not needed modules stay on the hard disc or the software repositories. | ||
| + | |||
| + | ==Modules== | ||
| + | |||
| + | |||
| + | ==Kernel Tools== | ||
Revision as of 16:09, 25 February 2020
Welcome to  Kernel Competence.
|
| Kernel Competence | ||
|---|---|---|
| Sysctl | Kldstat | Third-party Kernel Modules |
| Kernel Modules | FreeBSD Ports: Kld | Kenv |
| Compiling a new GhostBSD kernel | ||
Back to the  System
| ||
Contents
Introduction
On this page and its sub-pages we will collect all information connect to the kernel, like managing kernel modules, retrieve information from the kernel and use special commands.
Kernel
The kernel is the interface between the hardware and the software. The kernel lets the software write data to disk drives and to network. When a program needs memory, the kernel handles the access to the physical memory chip. When a program requests CPU time, the kernel organizes it. The kernel provides all the software interfaces that a program needs, in order to access hardware resources.
To follow the UNIX philosophy: to minimalist, modular software development the Ghost/FreeBSD kernel is set together out of modules. If a hardware requires a special piece of software, a appropriate module has to be loaded in to the working memory. Not needed modules stay on the hard disc or the software repositories.
