The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: Phil Budne <phil@ultimate.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: The Gnome and Its "Secret Place"
Date: Tue, 09 May 2023 03:32:17 +0000	[thread overview]
Message-ID: <KteNWoeISA1Jhzu3ODrA07uppB2szry8hdBck7d2H0V64yjzVzP9sO2rb9iOtjD2rQo11mYE1YHDrg-KTemQWbp-V0fTRzMC_Pn98Qwm5iI=@protonmail.com> (raw)
In-Reply-To: <202305082233.348MXrVC057305@ultimate.com>

> > In the midst of my documentation research, I've done a little analysis on the life and times of this whimsical little phrase which first appeared in the "HOW TO GET STARTED" or basinf section of the Third Edition manual (a derivative of the original login(VII) page):
> 
> > "When you type to UNIX, a gnome deep in the system is gathering your characters and saving them in a secret place."
> 
> 
> No sign of a login(VII) page in my "Program Generic PG-1C300 Issue 2"
> manual (no page, no entry in table of context, or permuted index).

By that point the quoted section was likely in the intro preceding the TOC and permuted index.  The login(VII) page only survived the first two editions, but portions of it were augmented into the secondary part of the introduction starting with the Third Edition manual.

https://gitlab.com/segaloco/v2man/-/blob/master/man7/login.7

vs

https://www.tuhs.org/cgi-bin/utree.pl?file=V3/man/man0/basinf

This basinf file persisted until somewhere between V6 and V7 when it was merged with intro.

- Matt G.

  reply	other threads:[~2023-05-09  3:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  3:51 [TUHS] " segaloco via TUHS
2023-05-08 22:33 ` [TUHS] " Phil Budne
2023-05-09  3:32   ` segaloco via TUHS [this message]
2023-05-09  4:23     ` Warner Losh
2023-05-09  4:36     ` Phil Budne
2023-05-09  5:09       ` segaloco via TUHS
2023-05-09 13:31 ` A. P. Garcia

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='KteNWoeISA1Jhzu3ODrA07uppB2szry8hdBck7d2H0V64yjzVzP9sO2rb9iOtjD2rQo11mYE1YHDrg-KTemQWbp-V0fTRzMC_Pn98Qwm5iI=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=phil@ultimate.com \
    --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).