note: subject change
hi jonathan,
when not latexing or playing games, i'm usually not using X.
runlevels are not meaningful since they mean different things for
different operating systems. i'm guessing you don't use debian, so i
don't know what runlevel 3 means.
when doing anything of any
btw,
echo 1 /proc/sys/kernel/sysreq to enable
echo 0 /proc/sys/kernel/sysreq to disable
you most likely won't be able to delete this file (untested) because
these files are not real filesystem files. they are abstractions of
kernel data into a memory region which looks like a filesystem and
Thanks Mike, Bill, and Pete for some helpful comments. I actually found
my answer with a google search
(http://www.tldp.org/HOWTO/Remote-Serial-Console-HOWTO/security-sysrq.html).
Here it clearly states that Writing a 0 into /proc/sys/kernel/sysrq
will disable the magic SysRq key, so my
begin Mike Simons [EMAIL PROTECTED]
On Tue, Mar 18, 2003 at 12:54:01PM -0800, Jonathan Stickel wrote:
I now have magic sysrq enabled and have tested it succesfully from
console with ctl-alt-h. Now I am ready the next time Linux freezes on me.
Keep in mind sysrq works form inside X
On Tue, Mar 18, 2003 at 01:33:38PM -0800, Peter Jay Salzman wrote:
begin Mike Simons [EMAIL PROTECTED]
Keep in mind sysrq works form inside X too...
[...]
X can not trap or block those key sequences...
that is what it looks like when i type alt-sysreq-h from within X.
i would say
begin Mike Simons [EMAIL PROTECTED]
On Tue, Mar 18, 2003 at 01:33:38PM -0800, Peter Jay Salzman wrote:
begin Mike Simons [EMAIL PROTECTED]
Pete,
Type your Alt-Sysrq combo, then look at dmesg or
tail -f /var/log/kern.log. The command sequence is being run.
aiee... ok, you're
