<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Please add the ability to go into standby mode to systemd-sleep." href="https://bugs.freedesktop.org/show_bug.cgi?id=57793#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Please add the ability to go into standby mode to systemd-sleep." href="https://bugs.freedesktop.org/show_bug.cgi?id=57793">bug 57793</a> from <a class="email" href="mailto:kay@vrfy.org" title="Kay Sievers <kay@vrfy.org>"> Kay Sievers</a> <pre>(In reply to <a href="show_bug.cgi?id=57793#c6">comment #6</a>) > If the kernel exposes it, we want to too. There is absolutely no rule like that, often it is quite the opposite. There are many things which aren't "clean" in the kernel interfaces, and we should be very careful with such generalizations. :) In many cases userspace has more information than the kernel, has policy, configuration it can use, so it can be smarter than the kernel knobs, and we should really try that, if possible. > so adding a new verb will be cleanest/easiest to use. I don't really think so. It's a rather exotic use, and mainly to work around broken hardware and kernel setups. If needed, we could make it overridable by custom config, which of the kernel facilities to chose to suspend, but we should really not explode the verbs which tools, using the systemd interfaces will need to support.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>