-
capros
CapROS is an experimental operating system based on object-capabilities, derived from EROS, KeyKOS, and Gnosis. Ports exist for the Intel IA-32 and ARM9 architectures.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
As other people have said check out the KeyKOS and EROS single level stores, their design seems to be similar to what you're going for. KeyKOS and CaprOS (a followup to EROS) are available on Github, and there are academic papers that explain their design. The EROS single level store paper in particular is very detailed. PhantomOS also seems to have persistent processes, but I am not too familiar with its design.
As other people have said check out the KeyKOS and EROS single level stores, their design seems to be similar to what you're going for. KeyKOS and CaprOS (a followup to EROS) are available on Github, and there are academic papers that explain their design. The EROS single level store paper in particular is very detailed. PhantomOS also seems to have persistent processes, but I am not too familiar with its design.
As an example on how to persist Linux/Unix processes check out the Aurora single level store that extends FreeBSD (we also have a paper that outlines the main problems and provides an explanation of the design). Aurora expands an existing OS and prioritizes supporting Unix applications so it looks very different from the microkernel design you are going for, but the problems it solves are intrinsic to making applications persistent.