From: Ralf Baechle <ralf@oss.sgi.com>
To: Gordon McNutt <gmcnutt@ridgerun.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: console knowledge
Date: Sat, 2 Dec 2000 02:53:17 +0100 [thread overview]
Message-ID: <20001202025317.A4718@bacchus.dhis.org> (raw)
In-Reply-To: <3A27EAD6.83E03DFB@ridgerun.com>; from gmcnutt@ridgerun.com on Fri, Dec 01, 2000 at 11:15:50AM -0700
On Fri, Dec 01, 2000 at 11:15:50AM -0700, Gordon McNutt wrote:
> > /dev/console (as chardev 5/1) differs from another device in some important
> > ways:
> >
> > - When opened by a process without controlling tty it will not become a
> > CTTY even if the NOCTTY flag is not set.
>
> What do you mean by "controlling tty"?
> output, but perhaps you can clarify.
Controlling terminal is a fundamental UNIX term; you should check a good
UNIX book about it. The glibc info pages also have some words about it.
> And why is the distinction noted above important? I assume it has something
> to do with keyboard input/screen
Reread my posting, it describes some of the differences in the behaviour
of for example /dev/console and /dev/ttyS0 even though both refer to the
same device.
That could be different. The classic UNIX setup is sending /dev/console to
the printer on one serial and having the system's console terminal on
another. Any arbitrary device combination would be possible.
Ralf
prev parent reply other threads:[~2000-12-02 1:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 6:48 Indigo2 Kernel Boots!!! Jesse Dyson
2000-11-30 7:53 ` Klaus Naumann
2000-11-30 14:41 ` Jesse Dyson
2000-11-30 15:56 ` Keith M Wesolowski
2000-11-30 16:10 ` Kevin D. Kissell
2000-11-30 16:10 ` Kevin D. Kissell
2000-11-30 23:59 ` Ralf Baechle
2000-12-01 7:22 ` Kevin D. Kissell
2000-12-01 7:22 ` Kevin D. Kissell
2000-12-01 15:33 ` Harald Koerfgen
2000-12-01 17:53 ` Ralf Baechle
2000-12-01 18:15 ` console knowledge Gordon McNutt
2000-12-02 1:53 ` Ralf Baechle [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=20001202025317.A4718@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=gmcnutt@ridgerun.com \
--cc=linux-mips@oss.sgi.com \
/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.