Anonymous user
Modular Kernel: Difference between revisions
Jump to navigation
Jump to search
m
→How can such a system boot in first place ?: link to BFS
| [unchecked revision] | [unchecked revision] |
mNo edit summary |
m (→How can such a system boot in first place ?: link to BFS) |
||
Line 29:
Modularization must be done within certain limits if you still want your system to be able to boot. Pushing ''all'' the filesystems and device drivers (including boot device driver) into module will probably make the boot time a hard time. Following solutions can however be used:
* The kernel is provided with an extremely simple [[File Systems|filesystem]] (e.g. SCO's [[BFS]]) driver and that filesystem contains modules to access the rest of system storage (e.g. module for ATA, SCSI, EXT2FS, [[ReiserFS]], FAT, NTFS ...).
* The kernel comes with a built-in native file system driver and other storage modules as well as primary configuration files should be stored using that native filesystem. This was the approach followed by Linux, and as soon as some people decided to have [[ReiserFS|reiser]] everywhere, ext2-fs only kernels start having trouble on some machines.
* The bootloader knows it should not only load the ''kernel'' but also a collection of pre-configured modules so that the kernel only needs to check those pre-loaded modules and initialize them to access other modules and primary configuration files. This basically means that your bootloader is somehow an OS of its own such as [[GRUB]]
| |||