From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org
Subject: Re: Guixsd adds 2 hours to a BIOS time
Date: Wed, 22 May 2019 22:38:03 +0200 [thread overview]
Message-ID: <87ef4qrzro.fsf@nckx> (raw)
In-Reply-To: <CALStFoG7ZAZz0scR4L6rhXWU-6R0wVgBb9qrg3xOt9x8Rg+M0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
Adam,
Adam Mazurkiewicz wrote:
> I live in Poland and I set time in config.scm in this way:
> (...)
> (operating-system
> (host-name "s")
> (timezone "Europe/Warsaw")
> (locale "en_US.utf8")
>
> (keyboard-layout (keyboard-layout "pl"))
> (...)
> Then I changed Warsaw to Paris because both have the same
> timezone and
> DST (Daylight Saving Time).
>
> In both cases, Warsaw and Paris, Guixsd added two hours to the
> time
> that was set in computer BIOS. So the 'date' command in the
> terminal
> gave wrong time, to hours later.
This all sounds very… correct, to be honest.
Your ‘BIOS’ (hardware) clock should always be set to UTC, not your
local time. Imagine your computer moving its CMOS clock forward &
back twice a year. Or every time you travel to a different
timezone. It would look as silly and confused as the rest of us.
Put differently: the time displayed in your computer firmware's
setup utility *should* be 2 hours behind your watch. This is what
all modern operating systems (even Windows, I've been told, if you
ask it nicely) and other software expect. It's not specific to
Guix System¹.
Judging by the fact that your e-mail arrived tomorrow, I'm
guessing that's not currently the case.
Kind regards,
T G-R
[1]: Previously known as ‘GuixSD’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-05-22 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 22:18 Guixsd adds 2 hours to a BIOS time Adam Mazurkiewicz
2019-05-22 20:38 ` Tobias Geerinckx-Rice [this message]
2019-05-24 17:27 ` Adam Mazurkiewicz
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=87ef4qrzro.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.