The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Of /dev/tty8
Date: Mon, 18 Mar 2024 20:17:28 +0000	[thread overview]
Message-ID: <iFsCdnB-SUswPfQ70tAT059iVw2b7MmmiPzxrZs8Rxb9gPyA_9poUST5UDWW1juOfEF6zUChhTkl8oR5Dr3wrZP0lt3-X3OuJqMSLoSJhm0=@protonmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2403190634060.86416@aneurin.horsfall.org>

On Monday, March 18th, 2024 at 12:36 PM, Dave Horsfall <dave@horsfall.org> wrote:

> On Mon, 18 Mar 2024, Ron Natalie wrote:
> 
> > /dev/tty existed in Version 6 for sure. It wasn't the console but
> > rather a magic device that mapped to the processes "controlling
> > terminal."
> 
> 
> I was referring to /dev/tty8, not /dev/tty...
> 
> -- Dave

ttys(V) in the Sixth Edition indicates the first digit of an /etc/ttys entry indicates a terminal line is active on init and the second indicates the final character of the /dev/ttyx entry[1].  Looking at both the Fifth and Sixth Edition /etc/ttys in the archive[2][3], both only have a 1 in the first column of entry 8, corresponding with /dev/tty8.

From the setup document distributed with the Sixth Edition[4]:

"The same goes for the character devices.
Here the names are arbitrary except that
devices meant to be used
for teletype access should be named
/dev/ttyX, where X is any character.
The files tty8 (console), mem, kmem, null are
already correctly configured."

From all of this it appears that by convention, tty8 was indeed the default console /dev entry, although this could be changed by editing the conf and ttys entries followed by regeneration of the system.  This would change in the Seventh Edition with the rearrangement of the ttys file to indicate longer /dev entry names and the establishment of a specific /dev/console entry.

- Matt G.

[1] - https://www.tuhs.org/cgi-bin/utree.pl?file=V6/usr/man/man5/ttys.5

[2] - https://www.tuhs.org/cgi-bin/utree.pl?file=V5/etc/ttys

[3] - https://www.tuhs.org/cgi-bin/utree.pl?file=V6/etc/ttys

[4] - https://www.tuhs.org/cgi-bin/utree.pl?file=V6/usr/doc/start/start

  reply	other threads:[~2024-03-18 20:17 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 [this message]
2024-03-18 13:56 ` Clem Cole
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='iFsCdnB-SUswPfQ70tAT059iVw2b7MmmiPzxrZs8Rxb9gPyA_9poUST5UDWW1juOfEF6zUChhTkl8oR5Dr3wrZP0lt3-X3OuJqMSLoSJhm0=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=dave@horsfall.org \
    --cc=segaloco@protonmail.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).