From: Andrew Morton <akpm@osdl.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Configurable Magic Sysrq
Date: Fri, 29 Oct 2004 03:24:20 -0700 [thread overview]
Message-ID: <20041029032420.327d65dd.akpm@osdl.org> (raw)
In-Reply-To: <20041029101758.GA7278@atrey.karlin.mff.cuni.cz>
Jan Kara <jack@suse.cz> wrote:
>
> > Jan Kara <jack@suse.cz> wrote:
> > >
> > > I know about a few people who would like to use some functionality of
> > > the Magic Sysrq but don't want to enable all the functions it provides.
> >
> > That's a new one. Can you tell us more about why people want to do such a
> > thing?
> For example in a computer lab at the university the admin don't want
> to allow users to Umount/Kill (mainly to make it harder for users to
> screw up the computer) but wants to allow SAK/Unraw.
> Another (actually not so legitimate ;) example is that in e.g. SUSE
> kernels sysrq is turned off by default (some people are afraid that it
> could be a security issue) so most users have it turned off and hence
> when the computer deadlocks, there's no debugging output.
OK, fair enough. I'll merge the patch if you talk suse into enabling
sysrq-T and sysrq-P and sysrq-M by default ;)
next prev parent reply other threads:[~2004-10-29 10:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 9:39 [PATCH] Configurable Magic Sysrq Jan Kara
2004-10-29 9:46 ` Andrew Morton
2004-10-29 10:17 ` Jan Kara
2004-10-29 10:24 ` Andrew Morton [this message]
2004-10-29 20:09 ` Dave Jones
2004-10-30 6:45 ` Olaf Hering
2004-11-01 9:29 ` Jan Kara
2004-10-31 18:59 ` Pavel Machek
2004-10-29 11:34 ` Måns Rullgård
2004-10-29 13:35 ` Jan Kara
2004-10-29 13:44 ` Måns Rullgård
2004-10-29 14:33 ` Jan Engelhardt
2004-10-29 14:50 ` Jan Kara
2004-10-29 14:53 ` Jan Engelhardt
2004-11-01 9:09 ` Jan Kara
2004-10-31 18:52 ` Pavel Machek
2004-10-31 19:09 ` Dmitry Torokhov
2004-10-31 19:44 ` Pavel Machek
2004-10-31 19:12 ` Andreas Schwab
2004-11-01 0:52 ` Tim Connors
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=20041029032420.327d65dd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jack@suse.cz \
--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