Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.arch
Subject: Re: Privilege Levels Below User
Date: Sun, 9 Jun 2024 22:45:43 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 17
Message-ID: <v45ban$3rcpa$8@dont-email.me>
References: <jai66jd4ih4ejmek0abnl4gvg5td4obsqg@4ax.com>
	<Z9I8O.13$2JEf.11@fx14.iad> <5h%8O.4327$wDZ.776@fx48.iad>
	<v428v9$2o803$1@dont-email.me>
	<31da390bdfe8486e6878cdc6db9bd98c@www.novabbs.org>
	<v44p8k$3lugs$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 10 Jun 2024 00:45:43 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="1186807d38ad523ecdef8690d71c9c11";
	logging-data="4043562"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18DXFAB14tjaJrWbDhgMORC"
User-Agent: Pan/0.158 (Avdiivka; )
Cancel-Lock: sha1:oJBzFJK/UpVeviLMpl5y707feKw=
Bytes: 1858

On Sun, 9 Jun 2024 12:36:09 -0500, BGB wrote:

> OTOH: A 32-bit value in seconds will overflow in 2038, so isn't really
> sufficient at this point.

A signed 32-bit value overflows in 2038, an unsigned value gives you a 
little bit more breathing room.

32-bit builds of the Linux kernel already offer the option for a 64-bit 
time_t. And Debian, for one, is currently in the middle of transitioning 
its 32-bit builds to that.

How can I tell, on my 64-bit system? Because all the affected packages 
have acquired “t64” suffixes on their names, and this applies to all 
architectures. I think this is temporary, though: once everything is fully 
compatible again, the “t64” suffixes will disappear. Presumably in time 
for the next stable release.