All of lore.kernel.org
 help / color / mirror / Atom feed
From: Crutcher Dunnavant <crutcher@datastacks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Sticky/Key-Setable SysRq (resubmit)
Date: Thu, 11 Oct 2001 18:51:04 -0400	[thread overview]
Message-ID: <20011011185104.B32585@mueller.datastacks.com> (raw)
In-Reply-To: <20011009105251.A20842@mueller.datastacks.com> <9pvd04$9sd$1@cesium.transmeta.com> <3BC40C41.5040603@wipro.com>
In-Reply-To: <3BC40C41.5040603@wipro.com>; from balbir.singh@wipro.com on Wed, Oct 10, 2001 at 02:22:17PM +0530

++ 10/10/01 14:22 +0530 - BALBIR SINGH:
> 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

This gets into a realm of advanced/robust features which I want to add
when 2.5 opens up. I will remember it, but right now I not seeing any
traction on this at all.


-- 
Crutcher        <crutcher@datastacks.com>
GCS d--- s+:>+:- a-- C++++$ UL++++$ L+++$>++++ !E PS+++ PE Y+ PGP+>++++
    R-(+++) !tv(+++) b+(++++) G+ e>++++ h+>++ r* y+>*$

      reply	other threads:[~2001-10-11 22: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
2001-10-11 22:51     ` Crutcher Dunnavant [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=20011011185104.B32585@mueller.datastacks.com \
    --to=crutcher@datastacks.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 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.