From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.cs.ucla.edu (mail.cs.ucla.edu [131.179.128.66]) by sourceware.org (Postfix) with ESMTPS id BD3C13858D28 for ; Tue, 11 Apr 2023 21:41:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org BD3C13858D28 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=cs.ucla.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cs.ucla.edu Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id CB9F63C097AFA; Tue, 11 Apr 2023 14:41:47 -0700 (PDT) Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id da-xIkGseLBu; Tue, 11 Apr 2023 14:41:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 635243C09FA04; Tue, 11 Apr 2023 14:41:47 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cs.ucla.edu 635243C09FA04 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=9D0B346E-2AEB-11ED-9476-E14B719DCE6C; t=1681249307; bh=p75Ri/qmXyL9sHCP9wurgpdnh3VVZ9RLa1IBVRaIAqw=; h=Message-ID:Date:MIME-Version:To:From; b=QQgkiO8qGpw5DMQQvYT73HADxbt29V83wTHN66LPOGL41At8jtfnd9Dpw2E7PBALb qX9YY/OQBQzmRUO2mGWXYcF9LyVMxUdftmy01fr0kmXq5YSYhkY/KtWOkYg7/H7RAO p7jibabWBZ7zpK3ARB1xnpHuzYu1zhbsp+QpvFEmbS8H2BeKMiv5zRqP8yMIAj+azr s4nL+Oii2IJ8+44QOrtfXuBFr469b7SvxHCq7FzulIoX9lbv0Vg7pFr40RIMVlRwnC 4iMEbOcbM6GNuHYFyr6VwoEBi1Zau+AvzlEP+KgQ2gZvV0r2FeRHYwryGOrYuC6o9u g7SiEBpu42ULA== X-Virus-Scanned: amavisd-new at mail.cs.ucla.edu Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id lB-vazFhfj0V; Tue, 11 Apr 2023 14:41:47 -0700 (PDT) Received: from [131.179.64.200] (Penguin.CS.UCLA.EDU [131.179.64.200]) by mail.cs.ucla.edu (Postfix) with ESMTPSA id 3DF583C097AFA; Tue, 11 Apr 2023 14:41:47 -0700 (PDT) Message-ID: <99c1f0eb-da72-f760-d200-4318a2da8759@cs.ucla.edu> Date: Tue, 11 Apr 2023 14:41:46 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: 64-bit time_t and __WORDSIZE_TIME64_COMPAT32 Content-Language: en-US To: Thorsten Kukuk References: <0869a6f98f29405eb431f63db593c490@DB6PR04MB3255.eurprd04.prod.outlook.com> <20230208101125.GA5099@suse.com> <20230208102225.GA5543@suse.com> <7485b79473614eaa994d3ea79c91629a@DB6PR04MB3255.eurprd04.prod.outlook.com> <20230208103819.GA6177@suse.com> <901005ca-640f-3a8f-a199-c1374f3cf141@linaro.org> <20230214082409.GA29974@suse.com> <3230d2f8fa214c268cba52e699c14ae2@DB6PR04MB3255.eurprd04.prod.outlook.com> <20230216135920.GA1706@suse.com> <20230411114052.GA29920@suse.com> From: Paul Eggert Organization: UCLA Computer Science Department Cc: libc-alpha@sourceware.org In-Reply-To: <20230411114052.GA29920@suse.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,JMQ_SPF_NEUTRAL,KAM_NUMSUBJECT,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 4/11/23 04:40, Thorsten Kukuk via Libc-alpha wrote: > wtmp: see https://www.thkukuk.de/blog/Y2038_glibc_wtmp_64bit/ > > Even if many applications write wtmp entries in a chaotic or wrong way, > there is only one application from relevance reading it: last. Also, coreutils "who", "users", "pinky", and "uptime", e.g., the shell command: who /var/log/wtmp which is used on occasion (e.g., ). > For coreutils patches exist beside who points to which 404s. So I assume you're talking about ? These are proof-of-concept (e.g., "who" needs patching). Also, will the decision about whether the old or new format is used be something that the coreutils builder knows at compile time? or will it be something switchable by the ops staff at runtime, so (e.g.) "who" should be prepared to read either format?