From: dave at horsfall.org (Dave Horsfall)
Subject: [TUHS] Seeking wisdom from Unix Greybeards
Date: Fri, 27 Nov 2020 08:59:27 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2011270850450.48674@aneurin.horsfall.org> (raw)
In-Reply-To: <20201126145134.GB394251@mit.edu>
On Thu, 26 Nov 2020, Theodore Y. Ts'o wrote:
> To make this a bit more TUHS-focused, was there anything that had
> similar functionality which pre-dated Bill Joy and termcap in late 70's?
As I recall, one wrote code "knowing" that it was a VT-05 etc if you
wanted escape sequences; I dimly recall using a getty-like file to get the
terminal type. Thus, /dev/tty8 was invariably (but not always) the
dreaded VT-05 (one client used a Duckwriter as the console, because he
wanted a hard-copy of everything; one day, the system went berserk (a bad
sector smack on the error log) and so did the hard copy, as Unix
faithfully tried to record each error).
-- Dave
next prev parent reply other threads:[~2020-11-26 21:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 17:14 Grant Taylor via TUHS
2020-11-25 17:22 ` Ralph Corderoy
[not found] ` <20201126145134.GB394251@mit.edu>
2020-11-26 21:48 ` steffen
2021-02-10 18:57 ` Greg A. Woods
2021-02-10 22:26 ` Clem Cole
2021-02-24 22:20 ` Steffen Nurpmeso
2020-11-26 21:59 ` dave [this message]
2020-11-25 17:38 ` Larry McVoy
2020-11-25 18:00 ` Steffen Nurpmeso
2020-11-25 20:03 ` Steffen Nurpmeso
[not found] ` <CACYmRNAtdJu0ui=CgrEcWH6J3uikCh0=aCLNvk0+V29rypDBAg@mail.gmail.com>
[not found] ` <71fdfa2e-1483-4985-3f55-6760b3a84ec0@gmail.com>
[not found] ` <20201126182937.GN9589@mcvoy.com>
2020-11-26 23:14 ` erc
2020-11-26 23:23 ` lm
[not found] <20201126183746.DD93218C087@mercury.lcs.mit.edu>
[not found] ` <7DBB40AE-259D-494E-8ABF-2FE4D47F4052@iitbombay.org>
2020-11-26 19:02 ` lars
2020-11-26 21:56 ` steffen
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=alpine.BSF.2.21.9999.2011270850450.48674@aneurin.horsfall.org \
--to=tuhs@minnie.tuhs.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).