[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170728145448.GZ1627@brightrain.aerifal.cx>
Date: Fri, 28 Jul 2017 10:54:48 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] use UTC instead of GMT
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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
