systemd depends so heavily on a files it can not reboot

["Jóhann B. Guðmundsson"]

On 07/08/2013 04:02 PM, Adam Pribyl wrote:
> On Mon, 8 Jul 2013, "Jóhann B. Guðmundsson" wrote:
>
>> No need to open a discussion. SysRq is disable for are a reason and 
>> what you are propose allows anyone that sits at the keyboard to kill 
>> all process,reboot without syncing or authorization and all because 
>> you got a corrupted filesystem.
>
> OK, so the systemd people say, it is perfecly fine you can not reboot 
> via ctrl-alt-del (while it was always possible with init) ??? 

The files on the system got corrupted so by all means  explain to me how 
it was possible with init more so with then with systemd?

And which previous init system sysv or upstart ?

Or are you really saying you never manage to corrupt the legacy sysv 
init or upstart files so that's why it was always possible?


> and give me the advice to enable sysrq for the purpose,

Yes you always wanted to make it possible to reboot on a corrupted 
filesystem and it was pointed as an option to achieve just that

> and sysrq people say, it's not for users, we will not enable it, it is 
> dangerous.
>

Yes enabling it is not a good default for the distribution however 
administrators and users themselves can enable if they want to while 
being aware of the security risks of doing so.

JBG