mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: time_t assessment of what needs to be done
Date: Mon, 1 Jul 2019 17:36:43 -0500	[thread overview]
Message-ID: <1f99e482-5eaf-34e0-b2ec-025f0b4f4078@adelielinux.org> (raw)
In-Reply-To: <20190701201107.GA6060@brightrain.aerifal.cx>


[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]

On 07/01/19 15:11, Rich Felker wrote:
> The utmp structure has just enough reserved space to move ut_tv to the
> end and make it unconditionally 64-bit-time_t. This is also nice for
> mixed 32/64-bit systems. Of course musl's utmp stuff is nopped out
> anyway but the types should be fixed for users of third-party utmp
> tooling/libraries. Alternatively we could just change it, since it's
> not an app-libc ABI at this point as far as I can tell. Matching the
> current 64-bit layout might be more useful than changing both.

With my official distro hat on, I can say that we have no preference:

[quoting system/musl/APKBUILD]

        # replaced by utmps - don't allow apps to sneak use of no-ops
        rm "$pkgdir"/usr/include/utmp.h
        rm "$pkgdir"/usr/include/utmpx.h


With my official distro hat off, I don't know if musl is trying to be
compatible with glibc ABI here as well.  If so, you should see what
they're doing to the layout of the utmp structure, because most apps
will write the structure directly to the disk.


Best,
--arw

-- 
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-07-01 22:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 20:11 Rich Felker
2019-07-01 22:36 ` A. Wilcox [this message]
2019-07-04 19:07 ` Rich Felker

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=1f99e482-5eaf-34e0-b2ec-025f0b4f4078@adelielinux.org \
    --to=awilfox@adelielinux.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).