The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Teletype
Date: Fri, 15 Aug 2014 17:07:28 -0400	[thread overview]
Message-ID: <CAC20D2NCHZboBC5TkF3_W3eSDGS93RDzS_XH_NDrVA4CbHoq5g@mail.gmail.com> (raw)
In-Reply-To: <CAEvOwxVxq1D_qD2W5Mzpybo8VoL-z+F7CV_QSQr32s4+8hn85A@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3697 bytes --]

Brian,

The easiest thing is set up a BSD box of any flavor (I have a FreeBSD box
that used to have modems on it).   Then grab a USB to RS-232C cable if it
does not have a serial ports on it already.   Make sure there is a
getty/login configured for the port and your are set.   At that point you
can directly attach the terminal to the cable.    No need for the modem.

You will get the user effect, accept for the sounds of the modem connecting
and dealing with dialing itself.  If you wanted those, you could of course
put the terminal on a modem and connect the BSD system to a modem. Then
either use to two POTS lines if you want to spend money from the TPC.
Actually thinking about, you could also set up a POTS line emulator (which
if you google you can make one pretty easily).

Funny, just this AM, I put into the the electronics recycling box at work 4
telebit "Worldblazer" modems and a POTS line emulator (and a bunch of other
old junk).   I've been clean out my basement and I knew I would never use
those again.

Clem


On Fri, Aug 15, 2014 at 2:52 PM, Brian Zick <brian at zickzickzick.com> wrote:

>
> On Fri, Aug 15, 2014 at 11:27 AM, Lyndon Nerenberg <lyndon at orthanc.ca>
> wrote:
>
>>
>> On Aug 15, 2014, at 11:04 AM, Brian Zick <brian at zickzickzick.com> wrote:
>>
>> > Would it still be possible today for someone like me to go out, and
>> find an old teletype terminal (an old ASR or DECwriter or something), set
>> up a phone line and modem and get a roll of paper, and then actually use it
>> to connect to other computers?
>> >
>> > I know it's not really practical today - but is it possible?
>>
>> Certainly it's possible.  Although you would really only be able to do it
>> with an ASCII terminal.  A DECwriter would work fine.  For a Teletype
>> beast, you would need to make sure it used ASCII.  But lacking lower case,
>> I think you would find it too painful to use, even though all the current
>> versions of UNIX (and Linux) I'm aware of still seem to support the
>> necessary case conversion in the tty drivers.
>>
>
> ​Hmm. So for a TTY that old there would probably be no option for
> lowercase. That does sound a little painful, especially if I wanted to edit
> modern programs..​
>
>
>> Your biggest obstacle might be finding a host machine that still has a
>> modem attached that you could dial in to :-)
>>
>
> ​So perhaps I could simplify it and attach to a machine sitting next to
> the TTY - which then in theory could connect to the outside world via the
> usual means. I wonder, has anyone tried something like this?
> ​
>
>> And, of course, everyone KNOWS the entire universe runs in terminals that
>> support ANSI escape sequences for colour and cursor positioning.  Who needs
>> termcap?  (I'm looking at you, git. And clang.)  So you might find setting
>> TERM=dumb isn't quite enough.
>>
>> Also, ed(1) is a wonderful editor on a hardcopy terminal.  Unless you run
>> it on Linux, which KNOWS the whole world runs on 24 line terminal windows,
>> and therefore ed needs to pause its output.
>
>
> ​I usually use vim, but before learning vim I learned ed and used it for
> about a 2 month space for editing config files and things, so that should
> hopefully be the easy part. :-)​
>
>
> Brian Zick
> zickzickzick.com
>
>      .:/
>   ,,///;,   ,;/
>  o:::::::;;///
> >::::::::;;\\\
>   ''\\\\\'' ';\
>      \
>
>
>
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140815/f0c642ed/attachment.html>


  parent reply	other threads:[~2014-08-15 21:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 18:04 Brian Zick
     [not found] ` <99C03A20-7BC3-44CA-946D-6CFD56B9346F@orthanc.ca>
2014-08-15 18:52   ` Brian Zick
2014-08-15 19:05     ` Ed Skinner
2014-08-15 19:13       ` Lyndon Nerenberg
2014-08-15 21:07     ` Clem Cole [this message]
2014-08-15 21:23       ` Hoskins, Matthew E.
2014-08-18  5:54       ` Brian Zick
2014-08-16 10:25     ` Dario Niedermann
2014-08-15 19:08 ` John Cowan
2014-08-15 19:16   ` Lyndon Nerenberg
2014-08-16 20:42   ` Ernesto Celis
     [not found] ` <CAEvOwxW=G+g3dtSGaN=P7QmovgOygfANxacmcUo9Devn6v6B1Q@mail.g mail.com>
2014-09-15 15:13   ` John Foust
2014-09-15 19:38     ` Dave Horsfall
2014-09-15 19:51     ` Cory Smelosky
2014-08-15 21:47 Noel Chiappa
2014-08-15 21:53 ` Warner Losh
2014-08-15 22:01 ` John Cowan
2014-08-16  1:56   ` Lyndon Nerenberg
2014-08-16  2:12     ` Lyndon Nerenberg
2014-08-16 21:28       ` Ronald Natalie
2014-08-15 21:55 ckeck
2014-08-16 14:35 Noel Chiappa
2014-08-17 17:33 Noel Chiappa
2014-08-18 13:56 Noel Chiappa

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=CAC20D2NCHZboBC5TkF3_W3eSDGS93RDzS_XH_NDrVA4CbHoq5g@mail.gmail.com \
    --to=clemc@ccc.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).