public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Marcelo Tossati <marcelo.tosatti@cyclades.com.br>, m.c.p@wolk-project.de
Subject: Re: [PATCH] Allow sysrq() via /proc/sys/kernel/magickey
Date: Fri, 19 Sep 2003 14:09:25 +0100	[thread overview]
Message-ID: <20030919130925.GA21000@redhat.com> (raw)
In-Reply-To: <200308252003.h7PK3EQq024312@hera.kernel.org>

On Mon, Aug 25, 2003 at 07:42:57PM +0000, Linux Kernel wrote:
 > ChangeSet 1.1114, 2003/08/25 16:42:57-03:00, m.c.p@wolk-project.de
 > 
 > 	[PATCH] Allow sysrq() via /proc/sys/kernel/magickey
 > 	
 > 	Hi Marcelo,
 > 	
 > 	sysrq() is a good thing to debug things, but unfortunately you need to have
 > 	physical access to the keyboard. My company for instance maintains tons of
 > 	remote machines and sometimes we need to do sysrq() too, but it's not
 > 	possible to do so the remote way.
 > 	
 > 	Attached patch enables emulation of the Magic SysRq key (Alt-SysRq-key) via
 > 	the /proc interface. Just echo the desired character into the file and there
 > 	you go.
 > 	
 > 	Patch from Randy Dunlap!
 > 	
 > 	It's in -wolk for a long time and also in some other kernel tree forks.
 > 	2.5/2.6 has almost the same (/proc/sysrq-trigger)

So why not make this compatible with existing behaviour, and use the
same name ? Seems this is deviating between 2.4 / 2.6 for no good reason.

		Dave

-- 
 Dave Jones     http://www.codemonkey.org.uk

      parent reply	other threads:[~2003-09-19 13:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200308252003.h7PK3EQq024312@hera.kernel.org>
2003-08-26  1:06 ` [PATCH] Allow sysrq() via /proc/sys/kernel/magickey Jeff Garzik
2003-09-19 13:09 ` Dave Jones [this message]

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=20030919130925.GA21000@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    --cc=marcelo.tosatti@cyclades.com.br \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox