All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@blue-labs.org>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: "D. Stimits" <stimits@idcomm.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: missing sysrq
Date: Fri, 08 Jun 2001 18:10:42 -0700	[thread overview]
Message-ID: <3B217792.8020405@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0106072239570.26171-100000@asdf.capslock.lan>

BTW, you ONLY need to echo 1 > /proc../sysrq if you use a distribution 
that puts a 0 there on init.

By default the kernel initializes with '1'.

David

>>>I compiled it, and the sysrq is definitely in the config. No doubt at
>>>all. I also use make mrproper and config again before dep and actual
>>>compile. Maybe it is just a quirk/oddball.
>>>
>>>D. Stimits, stimits@idcomm.com
>>>
>>Have you tried "echo 1 > /proc/sys/kernel/sysrq"?
>>You need both, compiled in and activation.
>>



  parent reply	other threads:[~2001-06-09  1:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-01  3:51 missing sysrq Dieter Nützel
2001-06-08  2:46 ` Mike A. Harris
2001-06-08  4:38   ` D. Stimits
2001-06-09  1:10   ` David Ford [this message]
     [not found] <Pine.LNX.4.10.10106011050380.2614-100000@coffee.psychology.mcmaster.ca>
2001-06-01 20:52 ` Dieter Nützel
2001-06-01 22:31   ` george anzinger
2001-06-01 22:58     ` Dieter Nützel
2001-06-01 23:13   ` H. Peter Anvin
2001-06-02 19:03     ` Alan Cox
2001-06-02 19:10       ` H. Peter Anvin
2001-06-02 22:08     ` Russell King
2001-06-02 22:10       ` H. Peter Anvin
2001-06-02 22:39         ` Russell King
2001-06-02 22:42           ` H. Peter Anvin
     [not found] <200106010338.VAA13405@totalrecall.idcomm.com>
2001-06-01 16:05 ` D. Stimits
  -- strict thread matches above, loose matches on Subject: below --
2001-05-31  7:13 D. Stimits
2001-05-31 21:43 ` Bernd Eckenfels
2001-05-31 23:48   ` D. Stimits
2001-06-08  2:50     ` Mike A. Harris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B217792.8020405@blue-labs.org \
    --to=david@blue-labs.org \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stimits@idcomm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.