docs(readme): 📚 Fix kernel type terminology
While Vesper strives to be as thin as possible it's not exactly an exokernel, but it's a very thin microkernel, dubbed nanokernel here.
This commit is contained in:
parent
7d03ea85a2
commit
af3dc82c76
|
@ -2,7 +2,7 @@
|
|||
|
||||
## About kernel
|
||||
|
||||
Vesper is a capability-based single-address-space exokernel, it tries to remain small and secure. To achieve this, kernel functionality is extremely limited - it provides only address space isolation and IPC, after bootup kernel does not allocate any memory itself.
|
||||
Vesper is a capability-based single-address-space nanokernel, it tries to remain small and secure. To achieve this, kernel functionality is extremely limited - it provides only address space isolation and IPC, after bootup kernel does not allocate any memory itself.
|
||||
|
||||
Exokernel's distinctive trait is that it provides mechanisms but not policies. Vesper tries to move as many policy decisions as possible to the library OS.
|
||||
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
* Copyright (c) Berkus Decker <berkus+vesper@metta.systems>
|
||||
*/
|
||||
|
||||
//! Vesper single-address-space exokernel.
|
||||
//! Vesper single-address-space nanokernel.
|
||||
//!
|
||||
//! This crate implements the kernel binary proper.
|
||||
|
||||
|
|
Loading…
Reference in New Issue