From: "David S. Miller" <davem@redhat.com>
To: david.balazic@uni-mb.si
Cc: matthias.andree@stud.uni-dortmund.de, linux-kernel@vger.kernel.org
Subject: Re: Simple local DOS
Date: Thu, 10 Jan 2002 05:56:51 -0800 (PST) [thread overview]
Message-ID: <20020110.055651.74749601.davem@redhat.com> (raw)
In-Reply-To: <3C3D9B2B.2DDB72CB@uni-mb.si>
In-Reply-To: <3C3D9B2B.2DDB72CB@uni-mb.si>
From: David Balazic <david.balazic@uni-mb.si>
Date: Thu, 10 Jan 2002 14:46:19 +0100
> all this is off-topic on linux-kernel,
non-root user locked up the console code. console code is part of kernel.
it is a kernel topic.
The real issue is that X has the console in an indeterminate state (it
probably just saved the VGA state and is outputting probing
information) but now it is blocked on terminal output due to the
"less".
There is nothing the kernel can do about what X is up to. The suid
wrapper for X can check if stdout/stderr is a pipe and refuse to run
if it is.
So really, it is in fact off topic for linux-kernel. Please take this
to the xfree86 lists, I'm sure they'll be more than happy to fix it.
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2002-01-10 13:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 13:46 Simple local DOS David Balazic
2002-01-10 13:56 ` David S. Miller [this message]
2002-01-10 13:57 ` Xavier Bestel
2002-01-10 14:04 ` David Balazic
2002-01-10 14:22 ` Jasper Spaans
2002-01-10 21:09 ` J Sloan
2002-01-10 14:07 ` Richard B. Johnson
2002-01-10 14:58 ` David S. Miller
2002-01-10 15:16 ` Richard B. Johnson
2002-01-10 21:10 ` J Sloan
2002-01-10 14:08 ` Matthias Andree
2002-01-10 14:22 ` Wakko Warner
-- strict thread matches above, loose matches on Subject: below --
2002-01-11 13:00 Zwane Mwaikambo
2002-01-11 18:03 ` J Sloan
2002-01-09 16:51 David Balazic
2002-01-09 21:50 ` Matthias Andree
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=20020110.055651.74749601.davem@redhat.com \
--to=davem@redhat.com \
--cc=david.balazic@uni-mb.si \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
/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