Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #185142 > unrolled thread
| Started by | Long Wind <longwind2@yahoo.com> |
|---|---|
| First post | 2017-08-14 06:10 +0200 |
| Last post | 2017-08-14 21:00 +0200 |
| Articles | 10 — 7 participants |
Back to article view | Back to linux.debian.user
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
why time in XP is wrong? Long Wind <longwind2@yahoo.com> - 2017-08-14 06:10 +0200
Re: why time in XP is wrong? David Christensen <dpchrist@holgerdanske.com> - 2017-08-14 07:10 +0200
Re: why time in XP is wrong? arne <sp113438@telfort.nl> - 2017-08-14 07:20 +0200
Re: why time in XP is wrong? Long Wind <longwind2@yahoo.com> - 2017-08-14 13:20 +0200
Re: why time in XP is wrong? Erik Christiansen <dvalin@internode.on.net> - 2017-08-15 13:10 +0200
Re: why time in XP is wrong? Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-08-14 20:10 +0200
Re: why time in XP is wrong? Joe <joe@jretrading.com> - 2017-08-14 20:30 +0200
Re: why time in XP is wrong? Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-08-14 20:50 +0200
Re: why time in XP is wrong? Joe <joe@jretrading.com> - 2017-08-14 22:00 +0200
Re: why time in XP is wrong? Felix Miata <mrmazda@earthlink.net> - 2017-08-14 21:00 +0200
| From | Long Wind <longwind2@yahoo.com> |
|---|---|
| Date | 2017-08-14 06:10 +0200 |
| Subject | why time in XP is wrong? |
| Message-ID | <ueeRr-7Me-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
my Debian share disk with XPit never cause wrong time problem in XP beforebut new Debian cause it in new Debian i choose correct timezone, time/date is OKbut time is wrong in XP maybe Debian thinks that bios is set universal time ??how to fix it?? Thanks!!
[toc] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2017-08-14 07:10 +0200 |
| Message-ID | <uefNv-8px-7@gated-at.bofh.it> |
| In reply to | #185142 |
On 08/13/17 21:03, Long Wind wrote:
> my Debian share disk with XPit never cause wrong time problem in XP beforebut new Debian cause it
> in new Debian i choose correct timezone, time/date is OKbut time is wrong in XP
> maybe Debian thinks that bios is set universal time ??how to fix it?? Thanks!!
Please enter the following commands into a Terminal in Debian, then cut
and paste the command and the output into your reply:
cat /etc/debian_version
uname -a
By "XP", please confirm you mean Windows XP.
Please explain how you are sharing a disk between Windows XP and Debian.
What file system is on the disk?
Please explain what you mean by "wrong time problem".
What timezone is the CMOS clock in your computer set to?
Please explain what you mean by "new Debian".
In what context did you "choose correct timezone"?
David
[toc] | [prev] | [next] | [standalone]
| From | arne <sp113438@telfort.nl> |
|---|---|
| Date | 2017-08-14 07:20 +0200 |
| Message-ID | <uefXb-8sK-3@gated-at.bofh.it> |
| In reply to | #185142 |
On Mon, 14 Aug 2017 04:03:30 +0000 (UTC)
Long Wind <longwind2@yahoo.com> wrote:
> my Debian share disk with XPit never cause wrong time problem in XP
> beforebut new Debian cause it in new Debian i choose correct
> timezone, time/date is OKbut time is wrong in XP maybe Debian thinks
> that bios is set universal time ??how to fix it?? Thanks!!
>
While Debian prefer to keep the hardware clock in UTC (this prevents
the need to change it on daylight savings and timezone changes) other
systems (like Windows) by default keeps the hardware clock synchronized
to local time. To keep the hardware clock sane and the time correctly
displayed by multiple systems they need to agree on which timezone the
hardware clock is kept at.
In Debian the timezone for the hardware clock is configured in the
file /etc/adjtime;
0.000000 14602224559 0.000000
1460224559
UTC
Edit /etc/adjtime, and change "UTC" to "LOCAL" if you want the hardware
clock to be kept at local time instead of UTC.
[toc] | [prev] | [next] | [standalone]
| From | Long Wind <longwind2@yahoo.com> |
|---|---|
| Date | 2017-08-14 13:20 +0200 |
| Message-ID | <uelzA-3tE-11@gated-at.bofh.it> |
| In reply to | #185148 |
[Multipart message — attachments visible in raw view] — view raw
thanks!but /etc/adjtime does not existdo i have to create it??
i use stretch
On Monday, August 14, 2017 1:12 PM, arne <sp113438@telfort.nl> wrote:
On Mon, 14 Aug 2017 04:03:30 +0000 (UTC)
Long Wind <longwind2@yahoo.com> wrote:
> my Debian share disk with XPit never cause wrong time problem in XP
> beforebut new Debian cause it in new Debian i choose correct
> timezone, time/date is OKbut time is wrong in XP maybe Debian thinks
> that bios is set universal time ??how to fix it?? Thanks!!
>
While Debian prefer to keep the hardware clock in UTC (this prevents
the need to change it on daylight savings and timezone changes) other
systems (like Windows) by default keeps the hardware clock synchronized
to local time. To keep the hardware clock sane and the time correctly
displayed by multiple systems they need to agree on which timezone the
hardware clock is kept at.
In Debian the timezone for the hardware clock is configured in the
file /etc/adjtime;
0.000000 14602224559 0.000000
1460224559
UTC
Edit /etc/adjtime, and change "UTC" to "LOCAL" if you want the hardware
clock to be kept at local time instead of UTC.
[toc] | [prev] | [next] | [standalone]
| From | Erik Christiansen <dvalin@internode.on.net> |
|---|---|
| Date | 2017-08-15 13:10 +0200 |
| Message-ID | <ueHTs-xi-19@gated-at.bofh.it> |
| In reply to | #185167 |
On 14.08.17 11:08, Long Wind wrote: > In Debian the timezone for the hardware clock is configured in the > file /etc/adjtime; > > 0.000000 14602224559 0.000000 > 1460224559 > UTC > > Edit /etc/adjtime, and change "UTC" to "LOCAL" if you want the hardware > clock to be kept at local time instead of UTC. I'm all for editing human-readable config files, but /etc/adjtime does not seem to entirely fit that category. I'd much rather follow the advice in "man tzselect", i.e. use "dpkg-reconfigure tzdata". That would leave me more confident that I'd not left loose ends. Erik
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-08-14 20:10 +0200 |
| Message-ID | <uerYm-7s4-11@gated-at.bofh.it> |
| In reply to | #185148 |
Le 14/08/2017 à 07:11, arne a écrit : > > To keep the hardware clock sane and the time correctly > displayed by multiple systems they need to agree on which timezone the > hardware clock is kept at. Setting the hardware clock to local time with multiple systems is broken if the time zone has daylight saving shifts. It cannot work, as each system will apply the shift without knowing another already did it. Windows 7 and later versions support setting the hardware clock to UTC through a registry setting. But with Windows XP the cleanest way is to use the UTC timezone or disable daylight saving shifts, or use NTP on each system to keep the system clock correct.
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2017-08-14 20:30 +0200 |
| Message-ID | <ueshH-7AC-3@gated-at.bofh.it> |
| In reply to | #185202 |
On Mon, 14 Aug 2017 20:09:19 +0200 Pascal Hambourg <pascal@plouf.fr.eu.org> wrote: > Le 14/08/2017 à 07:11, arne a écrit : > > > > To keep the hardware clock sane and the time correctly > > displayed by multiple systems they need to agree on which timezone > > the hardware clock is kept at. > > Setting the hardware clock to local time with multiple systems is > broken if the time zone has daylight saving shifts. It cannot work, > as each system will apply the shift without knowing another already > did it. > > Windows 7 and later versions support setting the hardware clock to > UTC through a registry setting. But with Windows XP the cleanest way > is to use the UTC timezone or disable daylight saving shifts, or use > NTP on each system to keep the system clock correct. > Even the latter may be a problem. I have a Win8 laptop that I occasionally boot to Sid, and of course it's an hour out back on Win8. But it is set to use NTP, however, there seems to be no control over how often it updates, and it certainly doesn't do it on boot. I always give up and use the admin password to trigger a sync, as a normal user can't do it. This seems to be the most likely answer, basically, add your own cron-equivalent job to do it independently of the Windows *once* *a* *week* scheduling. https://www.pretentiousname.com/timesync/ -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-08-14 20:50 +0200 |
| Message-ID | <uesB4-7Hs-19@gated-at.bofh.it> |
| In reply to | #185203 |
Le 14/08/2017 à 20:23, Joe a écrit : > On Mon, 14 Aug 2017 20:09:19 +0200 > Pascal Hambourg <pascal@plouf.fr.eu.org> wrote: >> >> Windows 7 and later versions support setting the hardware clock to >> UTC through a registry setting. But with Windows XP the cleanest way >> is to use the UTC timezone or disable daylight saving shifts, or use >> NTP on each system to keep the system clock correct. > > Even the latter may be a problem. I have a Win8 laptop that I > occasionally boot to Sid, and of course it's an hour out back on Win8. Why don't you set the hardware clock to UTC ?
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2017-08-14 22:00 +0200 |
| Message-ID | <uetGN-8je-1@gated-at.bofh.it> |
| In reply to | #185205 |
On Mon, 14 Aug 2017 20:44:47 +0200 Pascal Hambourg <pascal@plouf.fr.eu.org> wrote: > Le 14/08/2017 à 20:23, Joe a écrit : > > On Mon, 14 Aug 2017 20:09:19 +0200 > > Pascal Hambourg <pascal@plouf.fr.eu.org> wrote: > >> > >> Windows 7 and later versions support setting the hardware clock to > >> UTC through a registry setting. But with Windows XP the cleanest > >> way is to use the UTC timezone or disable daylight saving shifts, > >> or use NTP on each system to keep the system clock correct. > > > > Even the latter may be a problem. I have a Win8 laptop that I > > occasionally boot to Sid, and of course it's an hour out back on > > Win8. > > Why don't you set the hardware clock to UTC ? > Because one day, an update will change it back to default, and I'll spend four hours figuring out what's wrong. I've learned not to mess with Windows defaults without good reason, and resetting the clock five or six times a year isn't good enough. Every version of Windows gets more damn 'helpful'... I'm hoping Red Hat doesn't follow MS too closely... -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2017-08-14 21:00 +0200 |
| Message-ID | <uesKK-7KO-11@gated-at.bofh.it> |
| In reply to | #185202 |
Pascal Hambourg composed on 2017-08-14 20:09 (UTC+0200): > Setting the hardware clock to local time with multiple systems is broken > if the time zone has daylight saving shifts. It cannot work, as each > system will apply the shift without knowing another already did it. XP needn't be configured to adjust to time shifts. It's how all my few systems that still include XP, none of which are ever used for email, are configured. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web