Bug#761938: please stop breaking my system with systemd

[Gianluigi Tiesi]

Package: systemd
Severity: important

I've updated to systemd/udev 215-4, my system starts with a read-only
root, it has something to do with udev, mounting rw via kernel commandline,
or when a disk check occurs, workarounds the problem,
looks like a timing problem, but wait...
I'm unable to read the error because systemd is
                    SO BLAZING FAST!

really people, systemd and init scripts of many packages aren't just
ready for production.

I've rebuilt policykit removing systemd deps and my system magically
starts without any problems

and also:
- smartd daemon silently exits instead of starting
- transmission-daemon crashes
- I spin down my sdb disk, why hell it starts again at shutdown now?

If you want to play with systemd, just do it, but leave us an alternative,
please tell policykit maintainer to stop nazi mind and keep a non systemd
infected policykit.

Please stop this crazyness of forcing a non production-ready init system
or we'll just sit with pop-corn on jessie release wathing bug report storm.

Regards