From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jason Dravet <dravet@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: wrong number of serial port detected
Date: Thu, 8 Dec 2005 10:54:26 +0000 [thread overview]
Message-ID: <20051208105425.GA28397@flint.arm.linux.org.uk> (raw)
In-Reply-To: <BAY103-F5E97636877B8723077572DF420@phx.gbl>
On Wed, Dec 07, 2005 at 09:02:03PM -0600, Jason Dravet wrote:
> >As for your 64 VT tty device nodes - these "devices" are created
> >dynamically when the device node is opened. The act of opening the
> >device node is defined to be the creation event. If the device node
> >did not exist, there would be no way to create _any_ virtual terminals.
>
> I thought there were only 7 tty devices (Ctrl-F1 to Ctrl-F7) for local
> system login? Ctrl-F7 being for Xwindows. Did I miss something?
If you look in the "init" configuration file, /etc/inittab, you'll
see lines similar to these:
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
Once "init" has finished bringing up the rest of the system, it will
execute the mingetty commands, asking mingetty to open the first 6 ttys.
This opening of each tty creates the virtual console, at which point
you can switch to it.
If you add:
7:2345:respawn:/sbin/mingetty tty7
8:2345:respawn:/sbin/mingetty tty8
then you'll have login prompts on ctrl-f1 to ctrl-f8, and X will be
on tty9 (ctrl-f9).
You could even ask another program to send its output to /dev/tty12,
which you'll be able to view via ctrl-f12 - eg, I do this with the
system logger on some of my systems. At that point, you'll have
login prompts on tty1 to tty8, X on tty9 and something else on tty12.
(Note: you could comment out some of the mingetty lines in inittab,
but you should always leave at least one, in case something happens
with X and you need an alternative way to log in.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-12-08 10:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 3:02 wrong number of serial port detected Jason Dravet
2005-12-08 10:54 ` Russell King [this message]
2005-12-09 14:37 ` Jason Dravet
2005-12-09 17:27 ` Russell King
2005-12-09 19:54 ` Bjorn Helgaas
2005-12-10 1:46 ` Jason Dravet
2005-12-10 10:35 ` Russell King
2005-12-10 14:24 ` Jason Dravet
2005-12-10 15:46 ` Russell King
2005-12-10 17:56 ` Jason Dravet
-- strict thread matches above, loose matches on Subject: below --
2005-12-07 15:44 Jason Dravet
2005-12-07 15:50 ` Russell King
2005-12-07 19:59 ` Jason Dravet
2005-12-07 21:15 ` Russell King
2005-12-07 21:28 ` Xavier Bestel
2005-12-07 21:31 ` Russell King
2005-12-07 21:38 ` Russell King
2005-12-07 23:03 ` Dave Jones
2005-12-07 23:46 ` Russell King
2005-12-08 0:50 ` Dave Jones
2005-12-08 3:09 ` Dave Jones
2006-01-07 16:46 ` Russell King
2006-01-07 21:05 ` Dave Jones
2006-01-08 1:23 ` Jason Dravet
2006-01-08 9:08 ` Russell King
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=20051208105425.GA28397@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=dravet@hotmail.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