From: Tomko <tomko@avantwave.com>
To: linux-kernel@vger.kernel.org
Subject: Re: question about /dev/console and /dev/tty
Date: Mon, 30 May 2005 12:01:01 +0800 [thread overview]
Message-ID: <429A8FFD.40606@avantwave.com> (raw)
In-Reply-To: <d76sqc$suq$1@news.cistron.nl>
Hi,
Thank you very much for the reply, but i would like to ask some more.
1. it seems we can choose which device we want for console output by
typing this on kernel command line:
console = device , options
if i type "console = ttyS1 " is that means kernel will internally link
/dev/console to /dev/ttyS1 , and when i do any operation to /dev/console
, it is the same as i do to /dev/ttyS1 ?
2 . what means foreground virtual console as tty0 is representing ?
Regards,
TOM
Miquel van Smoorenburg wrote:
>In article <4296C5C0.4030409@avantwave.com>,
>Tomko <tomko@avantwave.com> wrote:
>
>
>>Hi everyone,
>>
>>Which device is /dev/console pointing to ? or is it a virtual device ?
>>Actually why this node is made?
>>
>>
>
>See linux/Documentation/serial-console.txt
>
>
>
>>Why kernel default not providing a control terminal on /dev/console but
>>on other device ?
>>
>>
>
>Because some daemons open /dev/console to send last resort error
>messages to, and you do not want them to unexpectedly gain a
>controlling tty.
>
>
>
>>It is not surprising that we can use CTRL-C to terminate some process on
>>i386 linux on the Desktop machine, is that mean the shell on our
>>desktop is not using /dev/console ? so where are the shell running on?
>>
>>
>
>/dev/tty1, /dev/tty2 etc
>
>Mike.
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
prev parent reply other threads:[~2005-05-30 4:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 7:01 question about /dev/console and /dev/tty Tomko
2005-05-27 10:29 ` Miquel van Smoorenburg
2005-05-30 4:01 ` Tomko [this message]
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=429A8FFD.40606@avantwave.com \
--to=tomko@avantwave.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.