public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Thorsten Kukuk <kukuk@suse.com>
To: libc-alpha@sourceware.org
Subject: Re: 64-bit time_t and __WORDSIZE_TIME64_COMPAT32
Date: Mon, 25 Sep 2023 07:30:58 +0000	[thread overview]
Message-ID: <20230925073058.GA21855@suse.com> (raw)
In-Reply-To: <8984748c-84f0-1ff7-77a5-ed0d1f372b86@linaro.org>



Hi,

a short update on this:

openSUSE Tumbleweed and MicroOS are using logind instead of utmp for
most applications since 1,5 week. An issue with uptime on Raspberry Pi's
is left (https://bugzilla.suse.com/show_bug.cgi?id=1215548), else there
are no open bug reports and it looks like majority of users did not even
noticed the switch :)
We still have the old files for compat reasons with the few not yet
adjusted packages, but I plan to remove them if we include systemd v255
and glibc allows to disable the interface.

Majority of patches are already upstream accepted, most of them even 
released.

I changed systemd so that systemd v255 will not use utmp but logind
internal, too.

I made presentations at All Systems Go! and OSS Europe and there I
received only positive feedback.
Especially "embedded" distributors were very interested in this (beside
the few people who think that 2038 is far, far away and we should not
care about this for the next decade).

On Tue, Apr 11, Adhemerval Zanella Netto via Libc-alpha wrote:

> I wonder if it would be better as a long term to add a switch 
> --disable-utmp (similar to --disable-crypt) which just set these functions
> to return ENOSYS without any compatibility support.  It is highly unlike 
> that we will ever get a proper fix for BZ#24492 [1] or add support for 
> 64-bit time_t for these interface, which are both either security or 
> usability issues.
> 
> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=24492

With the current state and feedback I think this is the best solution
for glibc going forward.
And for people who don't want to use systemd, there is still utmps and
similar projects, so utmp implementation outside of glibc.

  Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies
SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany
Managing Director: Ivo Totev, Andrew McDonald, Werner Knoblich
(HRB 36809, AG Nürnberg)

  reply	other threads:[~2023-09-25  7:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08  9:18 Thorsten Kukuk
2023-02-08 10:06 ` Andreas Schwab
     [not found] ` <0869a6f98f29405eb431f63db593c490@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:11   ` Thorsten Kukuk
2023-02-08 10:17     ` Andreas Schwab
     [not found]     ` <d2f1ee273add4af0868e07dc32542687@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:22       ` Thorsten Kukuk
2023-02-08 10:27         ` Andreas Schwab
     [not found]         ` <7485b79473614eaa994d3ea79c91629a@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:38           ` Thorsten Kukuk
2023-02-08 11:48             ` Adhemerval Zanella Netto
2023-02-14  8:24               ` Thorsten Kukuk
2023-02-14  8:59                 ` Florian Weimer
     [not found]                 ` <3230d2f8fa214c268cba52e699c14ae2@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-14  9:26                   ` Thorsten Kukuk
2023-02-14 14:28                     ` Adhemerval Zanella Netto
2023-02-16 13:59                   ` Thorsten Kukuk
2023-04-11 11:40                     ` Thorsten Kukuk
2023-04-11 13:23                       ` Adhemerval Zanella Netto
2023-09-25  7:30                         ` Thorsten Kukuk [this message]
2023-04-11 21:41                       ` Paul Eggert
2023-04-12  6:55                         ` Thorsten Kukuk
2023-04-12 23:36                           ` Paul Eggert

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=20230925073058.GA21855@suse.com \
    --to=kukuk@suse.com \
    --cc=libc-alpha@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).