From: Kirk Wood <cpt.kirk@1tree.net>
To: "speakup@braille.uwo.ca" <speakup@braille.uwo.ca>
Subject: Re: virtual consoles
Date: Sun, 22 Jul 2001 11:15:46 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0107221109340.6425-100000@ignatious> (raw)
In-Reply-To: <Pine.LNX.4.33.0107220436250.1782-100000@lnx1.holmesgrown.com>
There is a simple, logical reason for a default install to have only 6
virtual consoles. This leaves the other six function keys for switch to
the associated frame buffer. Now this probably doesn't mean much unless
you happen to be running X.
When you launch X from the first virtual console, the display is sent to
the frame buffer that is found at ALT-F6. While in X you can see the
console messages by pressing CTRL-ALT-F1. You could launch an X session
for each of the virtual consoles. In fact at least one distribution does
just that.
Given that few on this list will be running X anytime soon (other then to
a few programs to run), there should be no reason to not have more virtual
consoles. There is a slight trade-off in that each virtual console will
take a small amount of resources. But if you have a relatively new system,
you probably have an abbundance of resources and would never see the
difference.
=======
Kirk Wood
Cpt.Kirk@1tree.net
The mind is like a parachute; it works much better when open.
If you're too open minded, your brains will fall out.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Frank Carmickle
` Raul A. Gallegos
` Gregory Nowak
` Steve Holmes
` Steve Holmes
` Steve Holmes
` Kirk Wood [this message]
` Frank Carmickle
` Janina Sajka
Holmes, Steve
` Janina Sajka
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=Pine.LNX.4.21.0107221109340.6425-100000@ignatious \
--to=cpt.kirk@1tree.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).