From: Stuart Remphrey <stu@remphrey.net>
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 09:53:08 +0800 [thread overview]
Message-ID: <CAD0_1cmURG1LzDyBQhoddngjC-gcq-P0DV-94qvFGdsw0MAWzA@mail.gmail.com> (raw)
In-Reply-To: <54cd67b2-78f3-4ad3-a3c0-d0b885e67970@home.arpa>
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
Yes, tuhs.org:80 &443 could permanently redirect to www.tuhs.org so
browsers update to the full canonical name (assuming that's the desired
name).
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!)
On Tue, 14 Jun 2022, 00:44 Michael Kjörling, <michael@kjorling.se> wrote:
> On 13 Jun 2022 11:49 -0400, from norman@oclsc.org (Norman Wilson):
> >> Maybe make www.tuhs.org a CNAME for tuhs.org?
> >
> > Surely a site devoted to the history of UNIX should use a
> > real link, not a symbolic one.
>
> Surely a site that aims to collect information should have a single
> canonical name, not multiple ones that lead to the same content on the
> same host.
>
> I would suggest to pick either www.tuhs.org or tuhs.org as the HTTP
> hostname, and make the other redirect to the first (or remove HTTP
> service from the not-chosen one entirely) only so as to not break
> existing links from elsewhere.
>
> --
> Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
> “Remember when, on the Internet, nobody cared that you were a dog?”
>
[-- Attachment #2: Type: text/html, Size: 2443 bytes --]
next prev parent reply other threads:[~2022-06-15 1:53 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 [this message]
2022-06-15 5:57 ` Michael Kjörling
2022-06-15 12:04 ` Dan Cross
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=CAD0_1cmURG1LzDyBQhoddngjC-gcq-P0DV-94qvFGdsw0MAWzA@mail.gmail.com \
--to=stu@remphrey.net \
--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).