>If a bug is in systemd, I can't easily fix it myself. I now have to fight upstream to recognize my issue and fix it for me. That's not true. You can do as you

>If a bug is in systemd, I can't easily fix it myself. I now have to fight upstream to recognize my issue and fix it for me. That's not true. You can do as you would with the shell script and patch it in your local copy. If this is too much hassle then that shell script workflow shouldn't be broken by systemd and you can always fall back to it. It's still possible to run shell scripts as systemd units. You could also run another service manager as a systemd unit as another workaround. Also, in my experience, if you're fixing an actual crash, those patches are really likely to get accepted. Upstream appreciates that, I haven't seen them fight anyone over an easily verified issue. If you're submitting giant 10,000 line patches that change the public interfaces and cause regressions, that's a different story.