Mobeen Ahmed
Aevros: A Kernel That Explains Itself
Most educational kernels teach you how an operating system works. Fewer help you understand why something broke while you're experimenting.
Aevros started from that frustration. Instead of relying on external debuggers or cryptic panic messages, the kernel records information about its own state as it runs, making it possible to answer questions directly from within the system.
For example, rather than simply reporting that an allocation exists, Aevros can explain who created it and why it is still alive. Instead of printing raw page fault information, it translates the fault into a human-readable explanation. The goal is to reduce guesswork and make debugging feel more like asking questions than interpreting hex dumps.
Current features
- x86 boot process
- Physical memory manager
- Buddy and slab allocators
- Virtual memory and paging
- Cooperative scheduler
- ELF loader
- Virtual File System (VFS)
- System calls
- Interactive shell
- Built-in introspection tools
Introspection
The kernel records metadata when resources are created. That metadata powers commands that explain the running system rather than simply displaying raw state.
Some examples include:
-
health— overall system status -
whyalive— explains why a process still exists -
memstory— traces memory ownership -
blast— shows the impact of terminating a process
The goal isn't just to inspect the kernel, but to let the kernel explain itself.
Current development
The networking stack is currently being developed separately and will be integrated once it is stable. This avoids destabilizing existing subsystems while new functionality is being built.