How dzen25/psych-ward-os works
Psych Ward OS is documented as a seL4-based, event-driven microkernel OS. Its intended user-to-result flow is shell command → rootserver orchestration → isolated service or child process → IPC/VFS/device result, with watchdog recovery for failed services. The README names implementation files such as main.cpp and shell.cpp, but they are absent from the supplied tree; unsampled product components are therefore associated only with the existing user_apps/src directory. The kernel syscall implementation is present, but specific user-OS call relationships are documented rather than verified in its source.
Main entry points: user_apps/src Rootserver · syscall.c Kernel syscalls · kernel/src seL4 kernel
Components 15
Process control
- Shell
user_apps/src - Rootserver
user_apps/src - Process lifecycle
user_apps/src - Watchdog and GC
user_apps/src - IPC and pipes
user_apps/src
User services
- UART driver
user_apps/src - Timer driver
user_apps/src - Network driver
user_apps/src
I/O and storage
- Block driver
user_apps/src - VFS and FAT32
user_apps/src - Shared memory
user_apps/src - RAM disk
user_apps/src
seL4 kernel
- Kernel syscalls
kernel/src/api/syscall.c - seL4 kernel
kernel/src
Other components
- User
Connections 18
- User → Shell: enters commands
- Shell → Rootserver: sends requests
- Rootserver → Process lifecycle: manages processes
- Rootserver → Watchdog and GC: recovers services
- Rootserver → IPC and pipes: coordinates IPC
- Rootserver → UART driver: spawns driver
- Rootserver → Timer driver: spawns driver
- Rootserver → Network driver: spawns driver
- Rootserver → Block driver: spawns driver
- Shell → VFS and FAT32: resolves paths
- VFS and FAT32 → Block driver: reads storage
- Block driver → Shared memory: transfers sectors
- VFS and FAT32 → RAM disk: unifies filesystem
- Rootserver → Kernel syscalls: issues system calls
- Shell → Kernel syscalls: requests exec and wait
- Kernel syscalls → seL4 kernel: dispatches calls
- Network driver → IPC and pipes: routes requests
- Timer driver → IPC and pipes: signals events