On Tue, Apr 01, 2025 at 03:27:05PM -0400, Michael Stone wrote: > /run/utmp is no longer provided in trixie, which means that the mechanisms > used to show active sessions in unix for several decades no longer work. > There's a replacement mechanism provided by systemd, but it's not 1:1. I > propose that for trixie *both* mechanisms are active, so a person can choose > between them (and compare the output, to better identify gaps between the > historic utmp mechanism and the new and improved systemd facility). I've > been told that the reason this can't be done is that utmp isn't y2038 > compliant, but it seems to me that we won't be supporting trixie in y2038, > so who cares? Are there any factors to consider that I've missed?
I never cared about /run/utmp in itself, but I got used to last(1). FWIW, a new implementation of last is now provided by wtmpdb.
signature.asc
Description: PGP signature
