LinuxSA Mailing list archives

  From: Richard Russell <richard@austrics.com.au>
  To  : Michael Neuling <mneuling@radlogic.com.au>
  Date: Fri, 12 Nov 1999 14:16:10 +1030

Re: /proc/sys/kernel/sysrq

Michael Neuling wrote:

<snip my mail & mike's /proc explanation>

I had a feeling that that may have been the case...

> 
> BTW the SYSRQ option is a very useful option as you can unmount root
> when your machine is screwed therefore avoiding an fsck on
> reboot ....... not that Linux ever screws you machine :-)

OK, but supposing I didn't have it turned on (I don't) why would the
sysinit script be trying to write there -- am I to assume that the
sysinit script was written for a kernel with SYSRQ turned on, and that
that code is purely redundant? Interestingly, the code (see below)
appears to be turning SYSRQ off... Which implies to me that it is
writted to turn the feature off if it is compiled in, but there has been
no thought about what happens if it is not compiled in... 

-----------------------------------------
if [ "$MAGIC_SYSRQ" = "no" ]; then
        echo "0" > /proc/sys/kernel/sysrq
fi
-----------------------------------------

I assume I can do no harm by commenting these three lines out in sysinit
then?

Also, another related question about this... Where does $MAGIC_SYSRQ
come from? I assume it must be coming from somewhere, and must be "no",
otherwise this code would never get executed, and I would have no error
message...

thanks for the help

rr

-- 
 Richard Russell              | work:   +61 8 8207 1940
 AUSTRICS Transit Innovations | fax:    +61 8 8231 4821
 richard@austrics.com.au      | mobile:    0412 827 805
-- 
To boldly go.

-- 
LinuxSA WWW: http://www.linuxsa.org.au/  IRC: #linuxsa on irc.linux.org.au
To unsubscribe from the LinuxSA list:
  mail linuxsa-request@linuxsa.org.au with "unsubscribe" as the subject