From: Adam Mazurkiewicz <trzczy@gmail.com>
To: help-guix@gnu.org
Subject: Re: Guixsd adds 2 hours to a BIOS time
Date: Fri, 24 May 2019 19:27:45 +0200 [thread overview]
Message-ID: <CALStFoHwDEsthFgU9W8-CJmB3cjLCd7-Bo_Dt=i78GA_cVkBtQ@mail.gmail.com> (raw)
In-Reply-To: <87ef4qrzro.fsf@nckx>
śr., 22 maj 2019 o 22:38 Tobias Geerinckx-Rice <me@tobias.gr> napisał(a):
>
> 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.
You are right. I have always been setting CEST in BIOS but it has been
wrong. Thanks, for your great advice, Tobias.
>
> Kind regards,
>
> T G-R
>
> [1]: Previously known as ‘GuixSD’.
Kind regards,
Adam
prev parent reply other threads:[~2019-05-24 17:31 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
2019-05-24 17:27 ` Adam Mazurkiewicz [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALStFoHwDEsthFgU9W8-CJmB3cjLCd7-Bo_Dt=i78GA_cVkBtQ@mail.gmail.com' \
--to=trzczy@gmail.com \
--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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).