> And I don't care. In my entire professional life I have never ever been bitten by this problem.
Well, I guess you hadn't been bitten by the recent ext4 problem either until recently. And besides, even if you haven't, others have been, see Cyberax' comment.
> Er, if that's happened your network interfaces have almost certainly been shut down as well. How on earth is systemd supposed to help here?
systemd helps because, unlike sysvinit, it can reliably terminate a service so you don't have to mess around with kill(1) in the first place.
> You don't get it. They don't fail for me.
Well, lucky you. They do fail for others. I've had at least one boot failure due to a broken init script myself. And it broke for others too, see Scott's blog entry.
> but it is more unstable than sysvinit PID 1,
So you keep saying. But where are all those bugs that supposedly crash systemd all the time? I'm not from Missouri, but you'll have to show me anyway.
Besides, as Cyberax and raven667 have pointed out, there's not actually a whole lot going on in systemd itself, most of the recent activity is in systemd-journald and systemd-logind, both of which don't have PID 1.