The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: "Michael Kjörling" <michael@kjorling.se>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Documentation for Unix 4.0
Date: Wed, 15 Jun 2022 08:04:07 -0400	[thread overview]
Message-ID: <CAEoi9W4GafpXVzsNS_FbrxQe2ec5cvXz8CcupdCXuXA9+EMuPg@mail.gmail.com> (raw)
In-Reply-To: <393a28d5-98d7-44f1-908d-e70d0e8790db@home.arpa>

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

On Wed, Jun 15, 2022, 1:57 AM Michael Kjörling <michael@kjorling.se> wrote:

> On 15 Jun 2022 09:53 +0800, from stu@remphrey.net (Stuart Remphrey):
> > Though I think Norman was drawing an analogy between A-records/hard links
> > and CNAME/symlinks, then observing that prior to 4.2BSD in 1983 there
> were
> > no symlinks only hard links, ditto CNAMEs in RFC-882, also 1983.
> > So if we're going back further, we shouldn't use them (it breaks down a
> > little when considering A-records though, since we can't easily not use
> > those!)
>
> By much that same line of reasoning, tuhs.org shouldn't have any MX
> records either because the MX RRtype was introduced as recently as in
> 1986 (Wikipedia puts it at RFCs 973 and 974 [1] but without wide use
> until "in the early 1990s"). Let alone a web presence because HTTP and
> HTML came along even later. :-)
>
> [1] https://en.wikipedia.org/wiki/MX_record#Historical_background


This definitely feels like it extends the joke a tad too far. :-)

        - Dan C.

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

  reply	other threads:[~2022-06-15 12:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06  1:40 [TUHS] " Warren Toomey via TUHS
2022-06-06  2:15 ` [TUHS] " Warner Losh
2022-06-06  9:19   ` arnold
2022-06-06  2:26 ` Larry McVoy
2022-06-06  9:20   ` arnold
2022-06-07 16:57     ` John Cowan
2022-06-07 19:32       ` G. Branden Robinson
2022-06-09 22:19         ` Derek Fawcus
2022-06-06  6:21 ` G. Branden Robinson
2022-06-06  9:26   ` arnold
2022-06-10  6:47 ` Ed Bradford
2022-06-10  7:31   ` [TUHS] Source code for SCCS (was Re: Re: Documentation for Unix 4.0) arnold
2022-06-10  8:38     ` [TUHS] " Matthias Bruestle
2022-06-10 10:03       ` arnold
2022-06-15  5:32         ` Stuart Remphrey
2022-06-10 14:22   ` [TUHS] Re: Documentation for Unix 4.0 Clem Cole
2022-06-10 19:24     ` John Cowan
2022-06-11  4:34     ` Ed Bradford
2022-06-11 14:43       ` Clem Cole
2022-06-12  5:45         ` Ed Bradford
2022-06-12  6:41           ` Warren Toomey via TUHS
2022-06-13 13:18             ` Jay Logue via TUHS
2022-06-13 15:49               ` Norman Wilson
2022-06-13 16:39                 ` Michael Kjörling
2022-06-15  1:53                   ` Stuart Remphrey
2022-06-15  5:57                     ` Michael Kjörling
2022-06-15 12:04                       ` Dan Cross [this message]
2022-06-16  7:45                         ` Tom Ivar Helbekkmo 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=CAEoi9W4GafpXVzsNS_FbrxQe2ec5cvXz8CcupdCXuXA9+EMuPg@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=michael@kjorling.se \
    --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).