All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Alan Shutko <ats@acm.org>, James Simmons <jsimmons@suse.com>
Cc: Pavel Machek <pavel@suse.cz>,
	Frédéric L . W . Meunier  <0@pervalidus.net>,
	linux-kernel@vger.kernel.org
Subject: Re: SysRq behavior
Date: Fri, 15 Dec 2000 00:34:05 +0100	[thread overview]
Message-ID: <20001215003405.A190@bug.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.21.0012111440460.296-100000@euclid.oak.suse.com> <871yve4i77.fsf@wesley.springies.com>
In-Reply-To: <871yve4i77.fsf@wesley.springies.com>; from Alan Shutko on Mon, Dec 11, 2000 at 07:05:48PM -0500

Hi!

> > Just played with this bug. It doesn't kill a login shell but does any
> > app running on it. I just went looking for where "Quit" is printed
> > out. When I press SysRq Quit is printed on the command line. Any ideas?
> 
> Not a bug.  Normally,. PrtSc will generate a ^\, which is the default
> value of stty quit.  Try
> 
> stty quit ^A
> cat
> 
> and hit PrtSc

Okay, perhaps then it is bad for PrtSc to generate such dangerous
combination by default. Still bug ;-).
								Pavel
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-15 10:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-09  6:24 SysRq behavior Frédéric L . W . Meunier
2000-12-10 23:04 ` Pavel Machek
2000-12-11 23:00   ` James Simmons
2000-12-12  0:05     ` Alan Shutko
2000-12-14 23:34       ` Pavel Machek [this message]
2000-12-17 10:34     ` Tuomas Heino

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=20001215003405.A190@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=0@pervalidus.net \
    --cc=ats@acm.org \
    --cc=jsimmons@suse.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.