From: Guy Harris <gharris@sonic.net>
To: James Cloos <cloos@jhcloos.com>
Cc: musl@lists.openwall.com, Time zone mailing list <tz@iana.org>,
Russ Allbery <eagle@eyrie.org>, Rich Felker <dalias@libc.org>
Subject: [musl] Re: Weird PST8PDT and EST5EDT behavior on Alpine Linux
Date: Fri, 8 Mar 2024 10:39:34 -0800 [thread overview]
Message-ID: <48EA6B36-2F38-470B-ACD4-D85F92ED0FC7@sonic.net> (raw)
In-Reply-To: <m3ttlj8j3y.fsf_-_@nitrogen.jhcloos.org>
On Mar 6, 2024, at 7:39 AM, James Cloos <cloos@jhcloos.com> wrote:
>>>>>> "RA" == Russ Allbery <eagle@eyrie.org> writes:
>
> RA> and it's probably time to assume everyone supports the Olson
> RA> identifiers.
>
> Operwrt, at least in general, does not.
I.e., it doesn't provide tzdb files, to save storage space on small embedded devices?
> (Nor does aix, if anyone still cares.)
According to at least one page on IBM's support web site, "The default timezone format for AIX 6.1 and AIX 7 is Olson Time":
https://www.ibm.com/support/pages/managing-time-zone-variable-posix
Is that no longer the case?
> I have a clock (actual hw clock) which uses ntp by way of an embedded
> mips board running a version of openwrt. It lack the ram and storage
> to use tzdb. So I have to use EST5EDT,M3.2.0/2:00:00,M11.1.0/2:00:00
> for the timezone. (The explicit /2:00:00 might be avoidable, but the
> use of self documenting data can be beneficial.)
If the desire here is to allow all users of a system to specify time zones using old-style TZ strings such as EST5EDT rather than either POSIX-style or tzdb-style strings, if the system in question can be used outside of a particular hardwired polity, that'll require some way for time zone rules to be specified.
If the desire here is to allow old-style TZ strings within a given polity - said polity probably being the US - to use old-style TZ strings, that could be done by hardcoding the rules for the US and use them, and, if the US changes the rules, distribute an update to the system.
> (I must say it was a bit anoying that the library kept the original
> definition of EST5EDT et alia rathar than moving with the legislation.
> But only a bit.)
To which library are you referring here?
next prev parent reply other threads:[~2024-03-08 18:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87edcqv69m.fsf@hope.eyrie.org>
2024-03-05 3:52 ` [musl] Re: [tz] " Đoàn Trần Công Danh
2024-03-05 4:31 ` Paul Eggert
2024-03-05 20:12 ` Rich Felker
2024-03-05 20:56 ` Russ Allbery
2024-03-05 21:37 ` [musl] Re: [tz] [musl] " Guy Harris
2024-03-05 22:03 ` Russ Allbery
2024-03-05 22:12 ` Guy Harris
2024-03-05 22:31 ` Russ Allbery
2024-03-06 15:39 ` James Cloos
2024-03-08 17:46 ` [musl] Re: [tz] " Paul Eggert
2024-03-08 19:02 ` Rich Felker
2024-03-09 0:09 ` James Cloos
2024-03-09 1:57 ` [musl] Re: [tz] [musl] " Guy Harris
2024-03-08 18:39 ` Guy Harris [this message]
2024-03-08 19:05 ` [musl] Re: [tz] " Paul Eggert
2024-03-09 0:03 ` [musl] " James Cloos
2024-03-06 0:47 ` [musl] Re: [tz] " Paul Eggert
2024-03-06 1:54 ` 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=48EA6B36-2F38-470B-ACD4-D85F92ED0FC7@sonic.net \
--to=gharris@sonic.net \
--cc=cloos@jhcloos.com \
--cc=dalias@libc.org \
--cc=eagle@eyrie.org \
--cc=musl@lists.openwall.com \
--cc=tz@iana.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.
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).