public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "BALBIR SINGH" <balbir.singh@wipro.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Sticky/Key-Setable SysRq (resubmit)
Date: Wed, 10 Oct 2001 14:22:17 +0530	[thread overview]
Message-ID: <3BC40C41.5040603@wipro.com> (raw)
In-Reply-To: <20011009105251.A20842@mueller.datastacks.com> <9pvd04$9sd$1@cesium.transmeta.com>

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

H. Peter Anvin wrote:

 >Followup to:  <20011009105251.A20842@mueller.datastacks.com>
 >By author:    Crutcher Dunnavant <crutcher@datastacks.com>
 >In newsgroup: linux.dev.kernel
 >
 >>Attached is the patch from last week which provides the sysrq system
 >>with the following:
 >>
 >>a toggleable 'sticky' flag in /proc, which makes the sysrq key work 
on bad
 >>keyboards, and through bad KVMs.
 >>
 >>the ability to set which key in /proc, which makes the sysrq key work on
 >>system _without_ a 'sysrq' key; like bad KVMs.
 >>
 >>I've gotten no tracktion on this in a week, so I'm resubmitting it.
 >>
 >
 >I think doing this through procfs might be reasonable, but a kernel
 >command line option would be absolutely mandatory.  If things are
 >crappy you might not get to the point of fidding with /proc.
 >
 >Also, I really think SysRq has nothing to do under "Kernel
 >Hacking/Kernel Debugging".  More than anything else it's a system
 >administration feature.
 >
 >	-hpa
 >

Also, when configuring the kernel you can decide not to have /proc 
mounted (although this is very rare), but it might happen, if somebody 
decided not to use it, so as suggested, I think a kernel command line 
option would be nice.

Balbir





[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 853 bytes --]

----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------


  reply	other threads:[~2001-10-10  8:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09 14:52 [PATCH] Sticky/Key-Setable SysRq (resubmit) Crutcher Dunnavant
2001-10-09 17:43 ` H. Peter Anvin
2001-10-10  8:52   ` BALBIR SINGH [this message]
2001-10-11 22:51     ` Crutcher Dunnavant

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=3BC40C41.5040603@wipro.com \
    --to=balbir.singh@wipro.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /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