Originally posted by haplo602
View Post
systemd is also very modular, so you can remove most features with compile options, making the effective size of systemd very small.
Basically, if the embedded system has too little permanent storage for systemd, Linux itself is only a marginally fit.
Secondly, embedded are much more than routers with only 4mb flash storage. There are probably millions of SmartTV's sold every month, and most of them runs Linux. Systemd is a prefect fit for such systems and probably much better that any internally maintained toolboxes that the SmartTV developers use.
systemd can also offer much better stability and robustness to embedded systems. It has a total supervising chain; a hardware watchdog supervises systemd itself, while systemd supervises all processes; if a process hang, it can be restarted automatically without user intervention. I think the many router owners who are used to restart their hanging routers once in awhile would appreciate such supervision.
Also, systemd is also easily capable of only running services when needed, so it only launches e.g. sshd or the http Web GUI when the user actually needs it, reducing overall drain on system resources.
All in all, systemd easily out-competes any other init systemd for embedded devices, and it enables advanced COTS features that are supported upstream, which reduce developer cost (time to market, maintenance) compared to in-house developed toolboxes.
Originally posted by haplo602
View Post
I will provide the link again for your perusal:
"Factory Reset, Stateless Systems, Reproducible Systems & Verifiable Systems"
Comment