Re: 64-bit time_t and __WORDSIZE_TIME64_COMPAT32

[Paul Eggert <eggert@cs.ucla.edu>]

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., <https://linuxhandbook.com/who-command/>).


> For coreutils patches exist beside who

<https://www.thkukuk.de/blog/Y2038_glibc_utmp_64bit/> points to 
<https://github.com/thkukuk/utmpx/tree/main/coreutils> which 404s. So I 
assume you're talking about 
<https://github.com/thkukuk/utmpx/tree/main/patches/coreutils>? 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?