From: Jim Van Zandt <jrv@vanzandt.mv.com>
To: blinux-list@redhat.com
Subject: Re: Screen capturing:
Date: Sun, 01 Dec 1996 22:17:06 -0500 [thread overview]
Message-ID: <199612020317.WAA00233@vanzandt.mv.com> (raw)
In-Reply-To: Your message of "Sat, 30 Nov 1996 09:31:20 GMT." <Pine.LNX.3.95.961130090634.3141A-100000@amasis.trin.cam.ac.uk>
In message <Pine.LNX.3.95.961130090634.3141A-100000@amasis.trin.cam.ac.uk>, Nik
hil Nair writes:
>There are some devices called /dev/vcs* and /dev/vcsa*. The numbers after
>those prefices are 0 or none for current VC, or any other number for that
>number VC, i.e. /dev/vcsa or /dev/vcsa0 uses the current VC, /dev/vcsa3
>uses VC 3.
>
>If you want to know about the file format, and if you can't find the
>documentation, ask me.
You can also do "man vcs". If you don't have that man page, then you
need to install a new set of man pages. If you find it confusing or
incorrect, please let me know. As it happens, I wrote that man page
:-).
- Jim Van Zandt
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Luke Davis
` Nikhil Nair
` AARON HOWELL
` site report William Loughborough
` Jim Van Zandt [this message]
` Screen capturing: Peter Nilsson
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=199612020317.WAA00233@vanzandt.mv.com \
--to=jrv@vanzandt.mv.com \
--cc=blinux-list@redhat.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 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).