---

Once up on a time….

crinit and cominit were designed with a strong embedded and automotive background.

On such devices the hardware and software is pretty fixed. Hence only limited dynamic detection of hardware is needed. The numbers of software components are also limited, as the function set is strictly focused. These factors leave a full featured system- and service-manager unnecessary complex.

With systemd a full-featured startup-management-tool is already available and has proven good performances in embedded systems. But this usually takes some remarkable optimizations efforts. And than there is security that asks for removing of any interpreters, of course including bash and python. And security asks for extended protection of the config files.

And thus the idea of crinit was born! Only the really needed features, be fast and secured, nothing else...

And here it was shown for the first time:

Presentation@FrOSCon 2023

LinkedIn Tech Paper crinit / cominit - booting Linux in a function-focused embedded environment

---