distributions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: distributions@lists.linux.dev, Thorsten Kukuk <kukuk@suse.com>
Cc: Eric Blake <eblake@redhat.com>
Subject: Re: Y2038, glibc and utmp/utmpx on 64bit architectures
Date: Fri, 03 Mar 2023 21:25:04 +0100	[thread overview]
Message-ID: <2761646.h9gRbJKcGU@nimes> (raw)
In-Reply-To: <20230303170729.GA4300@suse.com>

Thorsten Kukuk wrote:
> > I really don’t think it is appropriate to outright remove POSIX standard
> > interfaces from Linux, replacing them with non-standard systemd APIs.
> 
> Nobody wants to remove the current utmp code (ok, not quite correct,
> glibc developers plan to remove it from glibc, as it will stop working
> in a few years) and feel free to convert all the code out there to use
> the utmpx and not utmp interface.

I don't understand: Do the glibc developers plan to remove the utmpx
interface as well (together with utmp interface)?

If no, then
  - Why does your blog post https://github.com/thkukuk/utmpx/blob/main/Y2038.md
    say "It looks like the glibc developers don't want to solve this problem
    but instead deprecate the utmp.h/utmpx.h/lastlog.h interface."?
  - What about the '#if __WORDSIZE_TIME64_COMPAT32' in
    /usr/include/x86_64-linux-gnu/bits/utmpx.h ? Isn't it as nasty as the
    '#if __WORDSIZE_TIME64_COMPAT32' in
    /usr/include/x86_64-linux-gnu/bits/utmp.h ?

If yes, then
  - What is the point of your suggestion to "use the utmpx and not utmp
    interface", above?
  - Since there is no "FUTURE DIRECTIONS" in POSIX
    https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/functions/endutxent.html
    will the utmpx interface get deprecated in POSIX, or stay as it is?
    Is the Austin Group already involved?

Bruno




  parent reply	other threads:[~2023-03-03 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 10:46 Y2038, glibc and utmp/utmpx on 64bit architectures Thorsten Kukuk
2023-03-03 16:51 ` A. Wilcox
     [not found] ` <3067bd0ec5134b039cdb8be9db8da8e5@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-03-03 17:07   ` Thorsten Kukuk
2023-03-03 20:09     ` Anna
2023-03-03 20:25     ` Bruno Haible [this message]
     [not found]     ` <c420abff6abd43cabac8c2fa5d812091@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-03-03 20:55       ` Thorsten Kukuk
2023-03-03 22:11         ` Bruno Haible

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2761646.h9gRbJKcGU@nimes \
    --to=bruno@clisp.org \
    --cc=distributions@lists.linux.dev \
    --cc=eblake@redhat.com \
    --cc=kukuk@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).