3 ms·
> to save a tiny bit of startup performance That is absolutely not the reason for systemd to exist, it is an additional benefit. How was early-boot logging, er
by kaba0 6y ago
> to save a tiny bit of startup performance
That is absolutely not the reason for systemd to exist, it is an additional benefit. How was early-boot logging, error handling, dependency handling between services implemented before? At best only in some ad-hoc way, different on each distro.
The domain has an inherent complexity to it, init systems are not easy, there is no saving that. But I think systemd exposing the configurable parts in a declarative way is a net win over the previous solutions.
- guenthert 6y ago>> to save a tiny bit of startup performance > That is absolutely not the reason for systemd to exist If you read the original web document announcing systemd, one could come away with the impression that it was though (even if substantiated with quite questionable performance tests using virtual machines).
- kaba0 6y agoAccording to a core developer, it was a side effect of doing things the right way: http://0pointer.de/blog/projects/the-biggest-myths.html http://0pointer.de/blog/projects/the-biggest-myths.html