From: Matias Fonzo <selk@dragora.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] remaining steps for time64 switchover
Date: Sun, 27 Oct 2019 18:53:14 -0300 [thread overview]
Message-ID: <a457507f118acaffe65075b21c3163cf@dragora.org> (raw)
In-Reply-To: <20191027211422.GA16318@brightrain.aerifal.cx>
Hello Rich,
El 2019-10-27 18:14, Rich Felker escribió:
> On Sun, Oct 27, 2019 at 05:12:59PM -0300, Matias Fonzo wrote:
>> Hello Laurent,
>>
>> Can utmps work without s6?. I mean, independently of the init
>> system or distribution...
>
> Laurent could answer in better detail, but as a quick answer, there's
> no requirement from having s6 installed that you use it as your init
> system.
>
I thought so, but there could be a configuration-side requirement or
daemon (setup) to work properly, I don't know. We are using perp for
Dragora.
>
>
>> El 2019-10-27 05:32, Laurent Bercot escribió:
>> >>Or here. So, the story on utmpx: we can either
>> >>
>> >>1. match the current size on 32-bit archs, but move the timeval to
>> >> unused space at the end where a time64 version fits, or
>> >>
>> >>2. match the current size and layout of the 64-bit struct, making it
>> >> possible to share records between 32- and 64-bit processes on the
>> >> same machine.
>> >>
>> >>Keep in mind that this struct is not used anywhere in libc presently,
>> >>but normally it's used as a format for on-disk records.
>> >>
>> >>I'm kinda leaning towards option 2, but being that I don't use (and
>> >>hate) utmp, I'd rather hear opinions from people who do use it. Either
>> >>way time fields in existing data will break, so it's a question of
>> >>whether that one-time breakage is already sufficient to go a bit
>> >>further and get 32/64 compat afterwards.
>> >
>> >I don't use the libc's utmpx, but I maintain utmps, which is a secure
>> >implementation of utmp, including the definition of struct utmpx.
>> >I haven't been following the time64 thing closely. The current struct
>> >utmpx definition includes a struct timeval. Will it need to change,
>> >or will musl's struct timeval change be enough and naturally propagate
>> >so the struct utmpx will become time64-compatible?
>> >
>> >On-disk data is not a problem. On the distro that I know uses utmps
>> >(Adélie), the utmp/wtmp records, by design, do not survive a reboot,
>> >so a reboot will fix everything - and will be mandatory anyway on
>> >arches where the musl ABI changes.
>> >
>> >I'm not aware of any distribution that uses musl, doesn't use utmps,
>> >and still keeps on-disk utmpx records.
>> >
>> >--
>> >Laurent
next prev parent reply other threads:[~2019-10-27 21:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 2:46 Rich Felker
2019-10-21 12:43 ` Rich Felker
2019-10-27 4:15 ` Rich Felker
2019-10-27 4:26 ` Rich Felker
2019-10-27 8:32 ` Laurent Bercot
2019-10-27 14:53 ` Rich Felker
2019-10-27 20:12 ` Matias Fonzo
2019-10-27 21:14 ` Rich Felker
2019-10-27 21:53 ` Matias Fonzo [this message]
2019-10-27 23:27 ` Laurent Bercot
2019-10-28 21:31 ` Matias Fonzo
2019-10-28 22:22 ` Rich Felker
2019-10-29 19:52 ` Rich Felker
2019-10-29 19:53 ` Rich Felker
2019-10-29 23:08 ` 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=a457507f118acaffe65075b21c3163cf@dragora.org \
--to=selk@dragora.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).