From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] use UTC instead of GMT
Date: Fri, 28 Jul 2017 10:54:48 -0400 [thread overview]
Message-ID: <20170728145448.GZ1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <597B44AE.6050004@adelielinux.org>
On Fri, Jul 28, 2017 at 09:05:34AM -0500, A. Wilcox wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 28/07/17 08:00, Rich Felker wrote:
> > On Fri, Jul 28, 2017 at 02:35:10PM +0200, Natanael Copa wrote:
> >> I checked what FreeBSD, OpenBSD and GNU/Linux does when timezone
> >> is unset. Seems that they all use "UTC" so I think that makes
> >> most sense.
> >
> > That may well end up being the reasonable position. Let's see what
> > others have to say on the matter (hopefully without it getting too
> > much into bikeshedding).
>
>
> +100
>
> That is the sane and reasonable thing to do and the fact musl doesn't
> do that automatically has broken two kernel builds for me (minor
> annoyance, but still a real issue). The kernels boot but uname -a
> says "Sat Sep 13 23:57:23 Time zone not s" which cuts off the year.
> May seem silly but having to use Wolfram Alpha to calculate what year
> the 13th of September fell on a Saturday is a bit annoying when you're
> dealing with servers with long uptimes...
>
> (The answer is 2014 and I pulled that from an old log. Don't worry,
> I'm not actually running anything that old on anything.)
Do you know how the kernel ended up with "Time zone not s[et?]" there?
This seems like a separate bug that should be addressed somewhere.
Rich
next prev parent reply other threads:[~2017-07-28 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 9:19 Natanael Copa
2017-07-22 14:26 ` Rich Felker
2017-07-28 12:35 ` Natanael Copa
2017-07-28 13:00 ` Rich Felker
2017-07-28 14:05 ` A. Wilcox
2017-07-28 14:54 ` Rich Felker [this message]
2017-12-07 16:54 Natanael Copa
2017-12-07 21:22 ` A. Wilcox
2017-12-07 22:15 ` Natanael Copa
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=20170728145448.GZ1627@brightrain.aerifal.cx \
--to=dalias@libc.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).