From: pechter@gmail.com (William Pechter)
Subject: [TUHS] uucp setup
Date: Fri, 10 Mar 2017 18:09:28 -0500 [thread overview]
Message-ID: <e0f1d1b3-f6ff-2ce0-f485-80bb19d14aaf@gmail.com> (raw)
One note for those who've been away from 4.x for a while...
If you're using a console window for editing and you just wonder why the
full screen of the VT100 doesn't show up -- it's because the getty is
set down at 1200 baud for the good old LA120 DECwriter III.
Set /etc/ttys to 18console or 12console and it's expects 9600baud and
then vi will let you use full screen to edit.
Been a while since I ran a fake Vax under Unix.
Bill
reply other threads:[~2017-03-10 23:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e0f1d1b3-f6ff-2ce0-f485-80bb19d14aaf@gmail.com \
--to=pechter@gmail.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 NNTP newsgroup(s).