On Wed, 15 Apr 2015, Greg Kroah-Hartman wrote: > 'systemctl reboot' calls a bunch of other things to determine if you > have local access to the machine, or permissions to reboot the machine > (i.e. CAP_SYS_BOOT), and other things that polkit might allow you to do, > and then, it decides to reboot or not. That happens today, right? I > don't understand the argument here.
And what exactly is the argument that this is the way it should be implemnted? Why can't it just rely on the kernel to provide final answer to "to reboot or not to reboot, that is the question"? At the end of the day, it's the kernel that decides whether it will really ultimately ask the platform to reboot. If, for whatever reason (which might be completely invisible to userspace) kernel decides not to do so, userspace has to be able to recover from such failure in any case. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
