Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #256343
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: differences between hwclock <-> date due to time zone issues? ... |
| Date | 2023-03-25 00:20 +0100 |
| Message-ID | <GcYRr-eRzG-1@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <GcQTT-eMAm-3@gated-at.bofh.it> <GcTf3-eOau-3@gated-at.bofh.it> <GcXsm-eQCt-5@gated-at.bofh.it> <GcXC1-eQFu-1@gated-at.bofh.it> <GcXLH-eQXT-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> That works great for the Live OS, but not for the fixed-disk OS. If
> the Live OS sets the HW clock to local upon shutdown, but the fixed-disk
> OS expects the HW clock to be UTC, then the fixed-disk OS is wrong
> every time it boots after the Live OS.
AFAIK the Linux kernel is pretty careful not to change the *hour* of the
hwclock: when using NTP, it will tweak the seconds to keep the hwclock
in sync with the rest of the world, but leave the hours alone, so as to
preserve the timezone in use, regardless if it's the right one (UTC) or
something else.
I assume GNU/Linux distributions like Debian are similarly careful,
since dual booting with a Windows install that doesn't use UTC for the
hwclock was a very common use case at least some years ago.
Stefan
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
differences between hwclock <-> date due to time zone issues? ... Albretch Mueller <lbrtchx@gmail.com> - 2023-03-23 22:50 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Stefan Monnier <monnier@iro.umontreal.ca> - 2023-03-23 23:10 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Cindy Sue Causey <butterflybytes@gmail.com> - 2023-03-23 23:10 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Cindy Sue Causey <butterflybytes@gmail.com> - 2023-03-23 23:30 +0100
Re: differences between hwclock <-> date due to time zone issues? ... David Wright <deblis@lionunicorn.co.uk> - 2023-03-23 23:50 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Andy Smith <andy@strugglers.net> - 2023-03-24 15:50 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Albretch Mueller <lbrtchx@gmail.com> - 2023-03-24 18:20 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Greg Wooledge <greg@wooledge.org> - 2023-03-24 22:50 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Stefan Monnier <monnier@iro.umontreal.ca> - 2023-03-24 23:00 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Greg Wooledge <greg@wooledge.org> - 2023-03-24 23:10 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Stefan Monnier <monnier@iro.umontreal.ca> - 2023-03-25 00:20 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Albretch Mueller <lbrtchx@gmail.com> - 2023-03-25 01:10 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Max Nikulin <manikulin@gmail.com> - 2023-03-25 04:20 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Albretch Mueller <lbrtchx@gmail.com> - 2023-03-25 04:50 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Max Nikulin <manikulin@gmail.com> - 2023-03-25 06:00 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Max Nikulin <manikulin@gmail.com> - 2023-03-25 09:00 +0100
Re: differences between hwclock <-> date due to time zone issues? ... David Wright <deblis@lionunicorn.co.uk> - 2023-03-25 05:30 +0100
Re: differences between hwclock <-> date due to time zone issues? ... David Wright <deblis@lionunicorn.co.uk> - 2023-03-25 05:30 +0100
Re: differences between hwclock <-> date due to time zone issues? ... Felix Miata <mrmazda@earthlink.net> - 2023-03-25 05:50 +0100
csiph-web