4 ms·

Debian has ports to FreeBSD and HURD; systemd doesn't support anything but Linux. I would assume that this would make systemd a non-starter in Debian (especiall

Debian has ports to FreeBSD and HURD; systemd doesn't support anything but Linux. I would assume that this would make systemd a non-starter in Debian (especially since there are no technical reasons systemd couldn't be ported). There are also other issues. Yes, sysvinit doesn't parallelize scripts or do automatic dependencies. If that's all systemd fixed, I'm sure everyone would be for it. But systemd seems to be consuming everything in its path (logging, cron, etc), ignoring the well-proven and time-tested design tenet of "do one thing well".

makomk 12y ago
I think Debian's supported parallel script execution and dependency resolution on top of sysvinit for a while anyway. It's not a true dependency-based init because the dependencies are resolved at configuration time rather than runtime, but whether that matters depends on what you're doing.
the_why_of_y 12y ago
The reason why sysvinit runs on FreeBSD and HURD kernels is that those kernels have implemented the Linux procfs file system. https://teythoon.cryptobitch.de/posts/on-portability-of-init-systems/ https://teythoon.cryptobitch.de/posts/on-portability-of-init... Besides, none of these are release architectures, so why should their limitations restrict what features >99.9% of Debian users have available?