From: "Darrell Shandrow" <nu7i@azboss.net>
To: <speakup@braille.uwo.ca>
Subject: Re: a quick linux tip
Date: Thu, 22 Aug 2002 19:56:27 -0700 [thread overview]
Message-ID: <005601c24a50$ace01180$4bb87cce@NU7I> (raw)
In-Reply-To: <003001c24a43$2c1f7ac0$30a87dc2@desktop>
Hi Darragh,
How about using the ps command to locate the process for that console, then
using kill to get rid of it?
----- Original Message -----
From: "Darragh" <darraghoheiligh@eircom.net>
To: <speakup@braille.uwo.ca>
Sent: Thursday, August 22, 2002 6:06 PM
Subject: Re: a quick linux tip
> Hello,
> talking of things going wrong, does any one know how to pass the exit
> command to another console? it would be a handy thing to know about...
>
> Darragh
> ----- Original Message -----
> From: "Tyler Spivey" <tspivey8@telus.net>
> To: <speakup@braille.uwo.ca>
> Sent: Thursday, August 22, 2002 8:16 PM
> Subject: a quick linux tip
>
>
> > well, i decided to contribute my .02 to here, here goes:
> > on most linux systems, maybe some other unix systems,
> > there is a command called reset.
> > if your terminal gets messed up (o echoing of commands, etc)
> > or wierd things appear (hard to explain, but really odd things instead
of
> a shell prompt
> > for example), you can type reset at a shell prompt.
> > that usually fixes the problem if it's a terminal issue.
> > i don't know if this hapens on the linux console, but it happens to me
on
> my serial terminal.
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Spivey
` Darragh
` Terry D. Cudney
` Raul A. Gallegos
` Gregory Nowak
` Darrell Shandrow [this message]
` Gregory Nowak
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='005601c24a50$ace01180$4bb87cce@NU7I' \
--to=nu7i@azboss.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).