[1oooqooq]

the service syntax is the least of your concerns.

the windows service manager like UI of systemctl exploratory mode is one thing to tackle.

the lack of visibility on dependencies that are not obviously direct. or even relevant (like ssh depending on key generation at first boot, which depends on time, which depends on time sync, which depends on network target... which causes ssh to not get started, without any logs, if you don't have network... despite it not being the first boot... :mindblown)

i won't bother with whole list because 1. there's no alternative 2. "I'm just another systemd denier" like i wouldn't have to be using it from early on to accumulate so much grievances

[jamespo]

Why do you want ssh if you don't have network :)

[1oooqooq]

in fact i noticed this bug when ssh doesn't come up on qemu vms start on a laptop without wifi connection.

hardly Far from a 99% use case.

loopback address space is not enough for the network target

[alexeldeib]

have you seen systemd-analyze?

[usr1106]

systemd-analyze dot is nice in theory. In practice the sheer amount of dependencies makes the results difficult to use or understand.

That it's a mixture of before and requires (probably also wants, don't rememeber) does not make it easier.

Edit: Newer version have options to separate ordering from requirements. I don't think that existed on the system where I last used it.

[1oooqooq]

yes and it also fails to catch that. and when reported years ago it was dismissed as "debian is doing weird shit. nobody sane depends things like so"