From: jidanni on

Thanks for the fix, however SysRq still has two things that are
non-intelligible to the operator who is locked out of his on-line
reference manuals: "saK" and nice-all-"RT"-tasks. "oom" I suppose you
can leave as a mystery :-) ... but better not, else 4 years from now
I'll Be Back. Better add a comment to the code reminding authors that
the SysRq help messages might be printed in situations where the
operator is otherwise locked out of his computer, so cannot look up what
they mean, so they must be verbose.

Also I noticed that at the four year frequency that I end up using
SysRq, all I remember is that one is supposed to squeeze a combination
of keys that include SysRq and h to get started. Therefore perhaps
mention there in the help message, just what one is actually supposed to
press (the several ways too), so that ones second press will be more
exact, even though they just managed to press it. (Put the answer in the
new help message, not in a reply to me!)

Now that I haven't yet occupied the whole screen with my ideas for a
more verbose SysRq help message, you might also mention there in the
message how the user can page the output of some of the more verbose
commands so that they don't fly off the screen mostly. Or mention if it
is not possible.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)
More majordomo info at
Please read the FAQ at