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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 10941 invoked from network); 31 Dec 2020 16:10:04 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 31 Dec 2020 16:10:04 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id D81F79C2EB; Fri, 1 Jan 2021 02:10:01 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id E6FCD9C29A; Fri, 1 Jan 2021 02:09:40 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="dZYesFx8"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 529259C29A; Fri, 1 Jan 2021 02:09:38 +1000 (AEST) Received: from mail-qt1-f181.google.com (mail-qt1-f181.google.com [209.85.160.181]) by minnie.tuhs.org (Postfix) with ESMTPS id 81B2A9C28C for ; Fri, 1 Jan 2021 02:09:37 +1000 (AEST) Received: by mail-qt1-f181.google.com with SMTP id c14so13072217qtn.0 for ; Thu, 31 Dec 2020 08:09:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=UFq9YHcZgvEu79xzBEuTGmbXqGusP0fw4YGiVKA4E3g=; b=dZYesFx869Yd9+1kxxkK1PH9XVxh0dJ2MOTLCcpphEGaJjydxUxc4lL94GrzLXYQmI 6dyf669roRQTQ82AeNHUB2XMgxpcbHW0N5D3jKGJ6r3sfSK7U0l9Zm8rT5nYtXmwl3uc 1WEeFCFzouS/cLmuG3Cn1ri58qNefrF2wmdp+IvfUJled9pm9ayvx9PFGZpno7gxcK2/ 3ngVyTjc+uJHsrfkpHLvD+D3+0D7zOlfNxoYDTWGKpaHsAajTAEEF6USM9FA6Mui06iH MP8t50P0d9WiUcF0rOKC16pNtjDv922htWrhTze2R1Cd0i1NyLVrRM+5LQkamUwDfqWr w7bQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=UFq9YHcZgvEu79xzBEuTGmbXqGusP0fw4YGiVKA4E3g=; b=NfHAt2cwPss9M9ax9XSrj/wXKuGOq7L916NT5NMm6Io/dVSP2Qiu+34YP6MRwzcBkx qMcAEcRtM6PmzQBlpkuTcwEanaqYAONwpy75Ag4mChMRcDVQEDWLpXy0Z8HJyY6yrE8r gTFljtNPp5oSBVLmPYkD5oShHqFwipeRHkQFZuiKtcdJL0o6TObE/J5ATRGZkhgUm0TU 8nm6ySIoFiu+M3n01sdIxr7dM/9p4dIqN+WVjSvBgHvA3rykokI6mNq82HUyb1z8tco6 VHesH96vYTlP/CdkAZ4Vtq+3xt64BEpho/xvTN7i0nEYBV2kbWqRKpUS/agj8JJ6rh3U fPdg== X-Gm-Message-State: AOAM533g4JaDpHakesGpYDfBUyk/E2qPnX/LB47yD3hU+rrGCTdQUd23 /ISsDrI1VkzKXOssjvIJGuQMICsAzVQDnQ== X-Google-Smtp-Source: ABdhPJwAu2hAIRU6j3LH3hldzhDEd5qgpvS/CiPlhoG/IKdSjelcomF/YhAJ8I+QtgHjKWFbiWUw7w== X-Received: by 2002:a05:622a:88:: with SMTP id o8mr57519940qtw.241.1609430975828; Thu, 31 Dec 2020 08:09:35 -0800 (PST) Received: from ?IPv6:2600:8800:7c80:700:41f6:aab9:7fd2:16c5? ([2600:8800:7c80:700:41f6:aab9:7fd2:16c5]) by smtp.gmail.com with ESMTPSA id d3sm15947268qka.36.2020.12.31.08.09.34 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Dec 2020 08:09:35 -0800 (PST) From: Adam Thornton Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Date: Thu, 31 Dec 2020 09:09:33 -0700 References: <202012310810.0BV8ADZ3027195@freefriends.org> To: The Eunuchs Hysterical Society In-Reply-To: Message-Id: <950DAE25-BCAD-47EF-8FCE-A716271A3C25@gmail.com> X-Mailer: Apple Mail (2.3654.40.0.2.32) Subject: Re: [TUHS] The 2038 bug... 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: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" I=E2=80=99ll be 67 for the 2038 bug. Plenty of time to charge = ridiculous hourly rates for being the old curmudgeon who still keeps a = bunch of these systems running in his house for some combination of fun, = nostalgia, and challenge. My gut tells me that this is going to be far less of a big deal than = 2000. To (somewhat inaccurately) summarize: the problem with 2000 is that = there was (and is, and will be in 2038) a whole bunch of COBOL doing the = Really Important Stuff with two-digit year fields. Whereas, time_t is basically internal, right? Software is forever, but hardware, even with the best of intentions, = after about 40 years or so, starts getting difficult to keep running = (/pats Atari 2600 affectionately). So if you *can* rebuild the software for a newer architecture=E2=80=A6then= suddenly there=E2=80=99s a wider time_t and the 33d bit is suddenly 1 = but nothing breaks. And if you can=E2=80=99t, you=E2=80=99re probably = by that point running it in emulation anyway, at which point your = emulation environment can know that 1/1/1970 is really whatever/2038, = and your software is partying like it was just 1969. If you have need = to maintain linearly incrementing time in your application, you do the = sliding window thing that we did with COBOL and Y2K. Aside: the COBOL problem was made worse by IBM=E2=80=99s (IMHO very = good) decision to provide problem-state instruction compatibility all = the way from the (1964, IIRC) 360 to the present day, so for more than = half a decade, you can just drop your Big Important COBOL onto the = current incarnation of the 3x0/z and it=E2=80=99ll be perfectly happy. Adam=