The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Dave Horsfall <dave@horsfall.org>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Of /dev/tty8
Date: Mon, 18 Mar 2024 09:56:41 -0400	[thread overview]
Message-ID: <CAC20D2O=puTR4qxRvVS0i2oYqYTMEza=7scP5h+CfL0WYDroMw@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2403182158390.86416@aneurin.horsfall.org>

[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]

Dave --  As Ron pointed /dev/ty was part of UNIX early in the game. I'm
pretty sure it was in V5 but it might even go back to V3 or V4.

To your point on naming the first serial mux for the PDP-11 was the
DH11/DM11, a 16 port [full 'system unit' in the backplate]. The single
hex-height DZ board did not appear from DEC until 1977 at the earliest
(although my memory is that it was late 78).  The DZ11 is an eight-port mux
(with short pinned modem control and no DMA - both causing issues). If you
remember, the original 1979 AT&T V7 release tape does not even have a
driver for the DZ ( it's in the v7 addendum, which came out 6-9 months
later).

I don't know, but maybe tty8 was just simply that the DC11s had originally
been to the first eight serial ports, and the first DL/KL was tty8

I'm not sure why I think this ... my hazy memory is that DC11 was 0-7, the
DLs 8-15, and DHs started 16
That memory may be because when I set up the the Teklabs 11/70 with 6 Able
DH/DMs [which were 16 ports in a hex board each], I used that convention to
remember which board controlled which port.
ᐧ
ᐧ
ᐧ

On Mon, Mar 18, 2024 at 7:14 AM Dave Horsfall <dave@horsfall.org> wrote:

> Evenin' all...
>
> I have a vague recollection that /dev/tty8 was the console in Edition 5
> (we only used it briefly until Ed 6 appeared), but cannot find a reference
> to it; lots of stuff about Penguin/OS though...
>
> Something to do with 0-7 being the mux, so "8" was left (remember that
> /dev/tty and /dev/console didn't exist back then), mayhaps?
>
> Thanks.
>
> -- Dave
>

[-- Attachment #2: Type: text/html, Size: 3478 bytes --]

  parent reply	other threads:[~2024-03-18 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 11:13 [TUHS] " Dave Horsfall
2024-03-18 11:22 ` [TUHS] " Ron Natalie
2024-03-18 19:36   ` Dave Horsfall
2024-03-18 20:17     ` segaloco via TUHS
2024-03-18 13:56 ` Clem Cole [this message]
2024-03-18 14:58   ` Paul Winalski
2024-03-18 15:20     ` Larry McVoy
2024-03-18 20:08       ` Ron Natalie
2024-03-18 20:21         ` segaloco via TUHS
2024-03-18 22:39           ` Bakul Shah via TUHS

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='CAC20D2O=puTR4qxRvVS0i2oYqYTMEza=7scP5h+CfL0WYDroMw@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=dave@horsfall.org \
    --cc=tuhs@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).