From: Helge Hafting <helgehaf@aitel.hist.no>
To: "Karel Kulhavý" <clock@twibright.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AT Keyboard (was: Helge Hafting vs. make menuconfig help)
Date: Thu, 17 Jun 2004 00:30:35 +0200 [thread overview]
Message-ID: <20040616223035.GA7932@hh.idb.hist.no> (raw)
In-Reply-To: <20040615195903.A7813@beton.cybernet.src>
On Tue, Jun 15, 2004 at 07:59:03PM +0000, Karel Kulhavý wrote:
> > 4. From there, the key is propagated through tty and
> > console and ends up in your application. This application
> > might be X, which passes the key onto some program using X.
>
> I am insterested in the 4. itself.
>
> What's the console?
The console is the text interface you see when not running
X (the graphical user interface).
> I get a feeling that it's where kernel writes it's debug
> messages but sometimes
Yes, the console is also used for this.
> else I get a feeling it's the text output of the
> machine at all.
>
You can also have text output in an xterm, thats not the console.
Or even on real terminals connected to serial ports.
> And what are the ttys? And does the key go first into console and then tty,
> or the other way?
TTY = TeleTYpe interface. The machine may have quite a few different
text interfaces, one of them is special and is the console.
Helge Hafting
next prev parent reply other threads:[~2004-06-16 22:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 14:02 Helge Hafting vs. make menuconfig help Karel Kulhavý
2004-06-15 14:10 ` Jan-Benedict Glaw
2004-06-15 14:20 ` Karel Kulhavý
2004-06-15 14:41 ` Jan-Benedict Glaw
2004-06-15 17:21 ` Karel Kulhavý
2004-06-15 17:32 ` Jan-Benedict Glaw
2004-06-15 17:46 ` AT Keyboard (was: Helge Hafting vs. make menuconfig help) Karel Kulhavý
2004-06-15 18:37 ` Helge Hafting
2004-06-15 19:59 ` Karel Kulhavý
2004-06-15 20:13 ` Jan-Benedict Glaw
2004-06-16 22:30 ` Helge Hafting [this message]
2004-06-15 20:35 ` Helge Hafting vs. make menuconfig help Vojtech Pavlik
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=20040616223035.GA7932@hh.idb.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=clock@twibright.com \
--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
all inboxes | Powered by JetHome®