From: "Jeremy M. Dolan" <jmd@foozle.turbogeek.org>
To: David Ford <david@linux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc update/fixes for sysrq.txt
Date: Sun, 28 Jan 2001 15:21:56 -0600 [thread overview]
Message-ID: <20010128152156.A406@foozle.turbogeek.org> (raw)
In-Reply-To: <20010128051118.A7975@foozle.turbogeek.org> <3A740416.55E93274@linux.com>
In-Reply-To: <3A740416.55E93274@linux.com>; from david@linux.com on Sun, Jan 28, 2001 at 11:35:50AM +0000
On Sun, 28 Jan 2001 11:35:50 +0000, David Ford wrote:
> AFAIK, this hasn't ever been true. I have never had to specifically
> enable it at run time.
I was suspicious of that in the old doc but thought I'd leave it in...
Should have asked for feedback on it, but you caught it anyway, thanks!
Here's a patch against the first that simply removes the lines.
/jmd
--- Documentation/sysrq.txt~ Sun Jan 28 14:41:44 2001
+++ Documentation/sysrq.txt Sun Jan 28 14:41:52 2001
@@ -15,9 +15,6 @@
echo "0" > /proc/sys/kernel/sysrq
-Note that previous versions disabled sysrq by default, and you were required
-to specifically enable it at run-time. That is not the case any longer.
-
* How do I use the magic SysRq key?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On x86 - You press the key combo 'ALT-SysRq-<command key>'. Note - Some
-
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/
next prev parent reply other threads:[~2001-01-28 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 11:11 Jeremy M. Dolan
2001-01-28 11:35 ` David Ford
2001-01-28 21:21 ` Jeremy M. Dolan [this message]
2001-01-31 18:06 ` Alan Cox
2001-01-31 23:14 ` David Ford
2001-01-29 15:49 Jonathan Earle
2001-01-29 21:42 ` David Ford
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=20010128152156.A406@foozle.turbogeek.org \
--to=jmd@foozle.turbogeek.org \
--cc=david@linux.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
all inboxes | Powered by JetHome®