From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=HTML_MESSAGE, MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28644 invoked from network); 15 Jun 2022 01:53:32 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 15 Jun 2022 01:53:32 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id B1403406E2; Wed, 15 Jun 2022 11:53:27 +1000 (AEST) Received: from mail-pf1-f182.google.com (mail-pf1-f182.google.com [209.85.210.182]) by minnie.tuhs.org (Postfix) with ESMTPS id B8553406DC for ; Wed, 15 Jun 2022 11:53:22 +1000 (AEST) Received: by mail-pf1-f182.google.com with SMTP id e11so10117284pfj.5 for ; Tue, 14 Jun 2022 18:53:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HLMrIv0AgyR63Kt8W/YCYruu/2+uxFde+i68CiexGhY=; b=ASsEK3oslVKLUd4GL1xdsHwn8X7cjk4jRXja4A9MLqru54Nn/Iq2rqMtrofVEiOTcb NMzK2XrI+BbuDCEd5yoq9wNs5oJkohq2qB1V5nMJm8x1BFojCjsoJeDrhTTho7zvjVtj XnaFwtnnAoL9ZeWMkSctitTCgDByfuaxwgaa+BGk4+k9MPrMAEeM66aE88fGPy33UqW1 enLu2j3zz7Q7xt/gAphHImzpcmgKBjfJyIHTSrwWp5QKqVIV+xBe3iYimBxmt6A/ujvc emoN1rn9O9KkmcpLIZb/jmfeJW/NYudx0ZxXfmZWGFckmfpIsr1xjDxVcoch5Pf96Qy0 H2Nw== X-Gm-Message-State: AOAM532y3qa9yqSIVkolNRiX2B/abfZffu6b/PvaT/82ewsUY0pMCCd9 owMH19Yidh2xJ3ia+VA/szpTYiKX9I1kbnaAcQirfFbF X-Google-Smtp-Source: ABdhPJyW0aWhSdG2IryNwvSyCGLTAwCRzQRmzM4Yus25+aHTUVdBzjNwSISnnmoeQvadKZp8BqXtaEKoeRsC8sLblII= X-Received: by 2002:a63:692:0:b0:3fd:e23d:f7d5 with SMTP id 140-20020a630692000000b003fde23df7d5mr6860790pgg.323.1655258001896; Tue, 14 Jun 2022 18:53:21 -0700 (PDT) MIME-Version: 1.0 References: <165512630943.1470.17753618581265860679@minnie.tuhs.org> <8845BDF5A20243F3CD8C296C36066BB3.for-standards-violators@oclsc.org> <54cd67b2-78f3-4ad3-a3c0-d0b885e67970@home.arpa> In-Reply-To: <54cd67b2-78f3-4ad3-a3c0-d0b885e67970@home.arpa> From: Stuart Remphrey Date: Wed, 15 Jun 2022 09:53:08 +0800 Message-ID: To: =?UTF-8?Q?Michael_Kj=C3=B6rling?= Content-Type: multipart/alternative; boundary="00000000000036fb0e05e172c943" Message-ID-Hash: 3RFCRNYZJOTGRQN7WO2GJYAQDDPSVALQ X-Message-ID-Hash: 3RFCRNYZJOTGRQN7WO2GJYAQDDPSVALQ X-MailFrom: sturem0@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tuhs.tuhs.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: The Eunuchs Hysterical Society X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Documentation for Unix 4.0 List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --00000000000036fb0e05e172c943 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=C3=B6rling, wro= te: > 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=C3=B6rling =E2=80=A2 https://michael.kjorling.se =E2=80=A2 mic= hael@kjorling.se > =E2=80=9CRemember when, on the Internet, nobody cared that you were a do= g?=E2=80=9D > --00000000000036fb0e05e172c943 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes, tuh= s.org:80 &443 could permanently redirect to www.tuhs.org so browsers update to the full canonical name (as= suming that's the desired name).

= Though I think Norman was drawing an analogy between A-records/hard links a= nd CNAME/symlinks, then observing that prior to 4.2BSD in 1983 there were n= o 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=C3=B6rling, <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 th= e 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=C3=B6rling =E2=80=A2 https://michael.kjorling.se =E2=80=A2 michael@kjorling.se
=C2=A0=E2=80=9CRemember when, on the Internet, nobody cared that you were a= dog?=E2=80=9D
--00000000000036fb0e05e172c943--