> I believe Hubris doesn't even allow new kinds of processes at runtime; all possible executables must be determined at compile time. Correct. From [0]: "Hubr

> I believe Hubris doesn't even allow new kinds of processes at runtime; all possible executables must be determined at compile time. Correct. From [0]: "Hubris is an aggressively static system. The configuration file defines the full set of tasks that may ever be running in the application. These tasks are assigned to sections of address space by the build system, and they will forever occupy those sections. Hubris has no operations for creating or destroying tasks at runtime. Task resource requirements are determined during the build and are fixed once deployed. This takes the kernel out of the resource allocation business. Memories are the most visible resources we handle this way, but it applies to all allocatable or routable resources, including hardware interrupts and memory-mapped registers – all are explicitly wired up at compile time and cannot be changed at runtime." [0] https://cliffle.com/blog/on-hubris-and-humility/ https://cliffle.com/blog/on-hubris-and-humility/