The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Derek Fawcus via TUHS <tuhs@tuhs.org>
To: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: virtual consoles / Alt-Fx
Date: Tue, 14 Mar 2023 17:42:09 +0100	[thread overview]
Message-ID: <ZBCj4cTOIVAwngVE@clarinet.employees.org> (raw)
In-Reply-To: <CAC20D2N5bxcvRzbzOwx68o=yAgJVJmabFn8V6_P1k65zT6gT4A@mail.gmail.com>

On Mon, Mar 13, 2023 at 11:24:24AM -0400, Clem Cole wrote:
> The virtual consoles using the function keys predate Linux and 386BSD by a
> number of years.  I used them only early x86 Unix ports to the IBM PC such
> as Xenix.

I'm pretty sure that the 386 version of ISC UNIX I used on a PC in the '88/89
timeframe had them.  I vaguely recall it having a more awkward key sequence
than Linux for switching between consoles.

Here we go:
  https://virtuallyfun.com/2010/02/09/fun-with-interactive-unix/

"On a text console side, the OS has virtual consoles switchable via SYSRQ + F key. Console is on F8."

DF

  parent reply	other threads:[~2023-03-14 16:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 15:12 [TUHS] " Paul Ruizendaal via TUHS
2023-03-13 15:24 ` [TUHS] " Clem Cole
2023-03-13 15:27   ` Clem Cole
2023-03-13 16:17     ` Paul Winalski
2023-03-13 15:41   ` Warner Losh
2023-03-13 15:48     ` KenUnix
2023-03-13 15:48     ` Clem Cole
2023-03-13 16:14     ` Dan Cross
2023-03-13 17:26       ` Miod Vallat
2023-03-13 20:35         ` Dan Cross
2023-03-14 16:42   ` Derek Fawcus via TUHS [this message]
2023-03-14 22:46     ` Charles H Sauer (he/him)
2023-03-15  4:26       ` Heinz Lycklama
2023-03-13 15:27 ` Ralph Corderoy
2023-03-13 15:30 ` Warner Losh
2023-03-14  3:27   ` Rik Schneider
2023-03-13 15:33 ` Ron Natalie
2023-03-13 15:45   ` Heinz Lycklama
2023-03-13 17:04   ` Ralph Corderoy
2023-03-13 15:49 ` Brad Spencer
2023-03-17  8:14 ` Marc Donner
2023-03-14  3:33 Rudi Blom

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=ZBCj4cTOIVAwngVE@clarinet.employees.org \
    --to=tuhs@tuhs.org \
    --cc=dfawcus+lists-tuhs@employees.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;
as well as URLs for NNTP newsgroup(s).