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=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31901 invoked from network); 31 Dec 2021 18:18:11 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 31 Dec 2021 18:18:10 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id F41539D041; Sat, 1 Jan 2022 04:18:07 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 262259CF51; Sat, 1 Jan 2022 04:17:35 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="dhZAiViv"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id E51119CF51; Sat, 1 Jan 2022 04:17:30 +1000 (AEST) Received: from mail-oi1-f182.google.com (mail-oi1-f182.google.com [209.85.167.182]) by minnie.tuhs.org (Postfix) with ESMTPS id 57A3F9CF06 for ; Sat, 1 Jan 2022 04:17:30 +1000 (AEST) Received: by mail-oi1-f182.google.com with SMTP id v6so45332365oib.13 for ; Fri, 31 Dec 2021 10:17:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pAMmudld/m1mSQC2pX51fr2GAMVWFXcjwU78CY7kL1o=; b=dhZAiViv3hhPN6xqZIgBK0dskksoSGxNZS9aKqUFWxV6GgOhKpcWutjBEFwHc2VAb/ nX7n9qJs8cWMBdOlMrIneQ105z6EnqgP+omYgREt13zFxAP3pGelO8FUrxllOnQOCAzg wbDWv/VaHNMJi7+mbqv3/zDqLKeeCTk+PPD8ajUtAhz2wLEnPxR/yjeppne+MiHqO5Br ZeckZMT30Jywz8IntXK+wF1UqkNNT5U0HCXAxvwjD0BmRq8TmhyoHNCkTe2SEOfWNU8U UYyiGaTzMNyliBv7Ra+dGt6WLQlYp0fS+SLWw7Uo7Ggv3rApXfkXXGU6nTyjug1RjEr1 iIqw== 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=pAMmudld/m1mSQC2pX51fr2GAMVWFXcjwU78CY7kL1o=; b=wvfvvw72m3wKkQd8j1lR25HRU2NX3OVwcBifOMtbAwhtuVqRvrw3DPo/pcjQiF3r24 OXiTYzcjHYiPG2d+0koxTSle3+urq1TNIaRqIfxq1GJScQOIYOkSG2mbYDcpTMa24yau 2ZYKQGls1OXGCrmWzOUiAytcy1hzGO8wRlMdxmDTeFK3v/+zzmwwAU/gN0Zwug1mwhcg 8JCSfIA2n+EsErq7MiF/HVSyGrCJx7+PID1tCsQ/w2/Bqr2zRKQs6BNHgnCYfaqLiVCt EE5fEblW+z66H5Ek7kg5selN2ClWWFwHFVEzhT7Yw0Ds9/qFl2fghMY5HkVSMC6ajATf kw5w== X-Gm-Message-State: AOAM531I0aqriI1jo5C9c4rYF+DcujVrrFdHQa/YD5WG3njQHgFy2Cuc IJJBxvW4uayO4itGQS7bMnR5FeggThSoUs0Ludw= X-Google-Smtp-Source: ABdhPJxM9f+pITzF41IUJTKP5/LmHtXNM6mFYXUvDC+uN0nXLnlNThkeBy1cSlAK2gYsgt4U2H4+HY/u0OY9WZkSdok= X-Received: by 2002:a05:6808:643:: with SMTP id z3mr27707914oih.110.1640974649611; Fri, 31 Dec 2021 10:17:29 -0800 (PST) MIME-Version: 1.0 References: <20211230034512.B9B3718C08E@mercury.lcs.mit.edu> <97f563fa-5a17-424b-acc6-07cf127f496d@localhost> In-Reply-To: From: Dan Cross Date: Fri, 31 Dec 2021 13:17:18 -0500 Message-ID: To: Adam Thornton Content-Type: multipart/alternative; boundary="0000000000001357dc05d4752f43" Subject: Re: [TUHS] moving directories in svr2 X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --0000000000001357dc05d4752f43 Content-Type: text/plain; charset="UTF-8" On Fri, Dec 31, 2021, 10:54 AM Adam Thornton wrote: > Slightly older, but also slightly more fundamental to the system, you need > look no farther than Solaris's `/bin/sh` for an illustrated example of the > pros and cons of maintaining backwards compatibility. [snip] > Sun is not the exemplar here: the move from SunOS 4's BSD userland to Solaris 2's SVR4 broke tons of things. They didn't seem to mind that their customers had to pay the cost of adaptation. The Linux example is also a bit strange. The move from e.g. `ifconfig` and `netstat to `ip` and `ss` required lots of local retooling (I suppose some distros retain the older tools or let you install them as an option. I suppose one could always install `bash` on Solaris as a shell lingua franca, as well). Not to mention systemd. The point is, breaking changes are introduced all the time. - Dan C. --0000000000001357dc05d4752f43 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Dec 31, 2021, 10:54 AM Adam Thornton <athornton@gmail.com> wrote:
Slightly older, but also sl= ightly more fundamental to the system, you need look no farther than Solari= s's `/bin/sh` for an illustrated example of the pros and cons of mainta= ining backwards compatibility. [snip]
<= div dir=3D"auto">
Sun is not the exemplar here: = the move from SunOS 4's BSD userland to Solaris 2's SVR4 broke tons= of things. They didn't seem to mind that their customers had to pay th= e cost of adaptation.

Th= e Linux example is also a bit strange. The move from e.g. `ifconfig` and `n= etstat to `ip` and `ss` required lots of local retooling (I suppose some di= stros retain the older tools or let you install them as an option. I suppos= e one could always install `bash` on Solaris as a shell lingua franca, as w= ell). Not to mention systemd. The point is, breaking changes are introduced= all the time.

=C2=A0 = =C2=A0 =C2=A0 =C2=A0 - Dan C.

--0000000000001357dc05d4752f43--