From: David Balazic <david.balazic@uni-mb.si>
To: matthias.andree@stud.uni-dortmund.de,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Simple local DOS
Date: Thu, 10 Jan 2002 14:46:19 +0100 [thread overview]
Message-ID: <3C3D9B2B.2DDB72CB@uni-mb.si> (raw)
Matthias Andree (matthias.andree@stud.uni-dortmund.de) wrote :
> On Wed, 09 Jan 2002, David Balazic wrote:
>
> >
> > log in on some virtual terminal, then run the following line
> > in a bourne type shell, like bash :
> >
> > X 2>&1 | less
> >
> > A reboot "fixes" it. We want to reach windows level quality on desktop
> > after all, don't we ?
>
> You can also fix that by a remote login,
How do I pull a network connection and a terminal out of a hat ?
Where do I get the hat ?
read : it is a sandalone system.
> chvt,
how do I start chvt if I have a locked up console system ?
> or by just not piping X
I didn't do it on purpose to lock up my system and risk FS corruption
durin unclean reboot. I was interested in the server output and " 2>&1 | less"
is the logical way to do that.
I could also "solve" this problem by not running linux. And I can "solve" all
gcc bugs by not using gcc. Those are not solutions. Not to me at least.
> output into interactive programs. tail -f is a viable workaround -- and
tail -f ? what is the difference between :
$ X 2>&1 | tail -f
and
$ X
?
> 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.
> it's your own dumbness that makes
> you do these things. Better run kdm, gdm or xdm or something and you're
> not having this problem.
My own dumbness ? Did you also say that ping-of-death is not a problem ?
After all it is just the dumbness of people who send out broken ping packets,
no ? And if a computer crashes , businesses lose time and money, you pop up and
explain "no it is not really lost money/time, because it was caused by dumbness !".
--
David Balazic
--------------
"Be excellent to each other." - Bill S. Preston, Esq., & "Ted" Theodore Logan
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
next reply other threads:[~2002-01-10 13:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 13:46 David Balazic [this message]
2002-01-10 13:56 ` Simple local DOS David S. Miller
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=3C3D9B2B.2DDB72CB@uni-mb.si \
--to=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