Craig Sanders <cas@taz.net.au> writes:
if it was *just* an init system, then it wouldn't be a monolithic monstrosity resulting in a mono-culture. but it's also absorbing syslogging, cron, udev, console and login handling, automount, and everything else in sight.
I noticed yesterday that readahead-fedora (the only readahead currently in Debian) has been abandoned upstream because its functionality is now absorbed into pid 1.
an init system doesn't need to do all those things. it just needs to handle starting up daemons/services in the right order at boot time, and killing them later on shutdown or reboot.
Preferably one that's as simple as possible, because when (not if) it goes tits-up, you won't have enough of a system up to fix it remotely. (Modulo a BNC, which is an entire bag of different pain.) For me, systemd (and pulseaudio and avahi) boil down to: Lennart (claims to) solve problems I don't have. I could ignore avahi and pa, because I Don't Do Desktops. I can't ignore systemd because it's likely to end up on servers. And I know from past experience with cinit/minit that dropping in a distro-unsupported init is... nontrivial.