On Fri, Feb 28, 2014 at 12:21 PM, Claudio Freire firstname.lastname@example.org wrote:
Silently enabling suspension through a patch update is what's wrong here. The update should include a configuration that mimicks previous behavior (or at least some safe behavior).
Otherwise known as the principle of least astonishment: http://en.wikipedia.org/wiki/Principle_of_least_astonishment
systemd has violated it in the past as well... like when my Ethernet interface was randomly renamed from eth0 to ens33, and a box that was 1,200 miles away from here became unreachable over the network (thanks for that one).