From: David Ford <david@linux.com>
To: Jonathan Earle <jearle@nortelnetworks.com>
Cc: "'Jeremy M. Dolan'" <jmd@foozle.turbogeek.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc update/fixes for sysrq.txt
Date: Mon, 29 Jan 2001 13:42:51 -0800 [thread overview]
Message-ID: <3A75E3DB.C13C380F@linux.com> (raw)
In-Reply-To: <28560036253BD41191A10000F8BCBD116BDCE3@zcard00g.ca.nortel.com>
Jonathan Earle wrote:
> > 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.
>
> I'd suggest leaving those lines in; I've never had it enabled by default.
> I've run Debian and Redhat systems, and both had to have the option
> specifically turned ON via startup script - simply compiling it into a
> kernel did not enable it.
>
> Jon
I suggest compiling it in and booting with init=/bin/bash, mounting /proc
and checking the value. It is enabled by default. A few distributions have
a boot script that enables or disables it based on the sysconfig.
-d
--
There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum
-
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-29 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 15:49 [PATCH] doc update/fixes for sysrq.txt Jonathan Earle
2001-01-29 21:42 ` David Ford [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-28 11:11 Jeremy M. Dolan
2001-01-28 11:35 ` David Ford
2001-01-28 21:21 ` Jeremy M. Dolan
2001-01-31 18:06 ` Alan Cox
2001-01-31 23:14 ` 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=3A75E3DB.C13C380F@linux.com \
--to=david@linux.com \
--cc=jearle@nortelnetworks.com \
--cc=jmd@foozle.turbogeek.org \
--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