[mercurial]

I believe it's not about between magical in the general case, but about how you specify dependencies between services, an area where systemd and upstart work differently.

See the 'On Upstart' section here [1].

1: http://0pointer.de/blog/projects/systemd.html

[digi_owl]

Reminds me why slackware packages do not have dependency resolution, because it invariably breaks. This most often in the sense of X wants Y while Z wants Y+-1. And so you are at an impasse because the dependency resolver can't handle having two versions of Y installed at the same time.

A recent failure of systemd i have seen was related to NFS. For some reason systemd would yank the network down before dismounting NFS.

If you don't unmount NFS before taking down the network, it will sit there forever waiting for that final server response.

Another example was where while mount would happily ignore a flawed fstab entry but mount the rest, systemd would bail on the whole mount task and so halt the boot process.

[acdha]

> A recent failure of systemd i have seen was related to NFS. For some reason systemd would yank the network down before dismounting NFS.

This isn't specific to systemd – I had to deploy workarounds to the same bug in RHEL, Debian, Ubuntu, FreeBSD, etc.