Re: Correct: System Thinks Hardware Clock is UTC

2018-05-21 Thread Felix Miata
Michael Stone composed on 2018-05-21 10:05 (UTC-0400): > On Mon, May 21, 2018 at 09:55:42AM -0400, Felix Miata wrote: >>OS/2 and DOS AFAICT never got that option. A LAN that is a mix of LOCAL and >>UTC >>isn't fun, especially with one or more that can't not, which is what I have >>with >>a

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-21 Thread Patrick Bartek
On Mon, 21 May 2018 09:03:47 -0400 Greg Wooledge wrote: > On Sun, May 20, 2018 at 12:15:05PM -0700, Patrick Bartek wrote: > > > > Haven't > > > > installed any other OS on this system since Wheezy 5 years ago. > > Oh, good, then you can simply set the hardware cl-- I did

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-21 Thread Michael Stone
On Mon, May 21, 2018 at 09:55:42AM -0400, Felix Miata wrote: OS/2 and DOS AFAICT never got that option. A LAN that is a mix of LOCAL and UTC isn't fun, especially with one or more that can't not, which is what I have with a Linux STB providing no LOCAL option and multiple OS/2's providing no UTC

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-21 Thread Felix Miata
Michael Stone composed on 2018-05-21 09:10 (UTC-0400): > On Sun, May 20, 2018 at 12:15:05PM -0700, Patrick Bartek wrote: >>Unfortunately, I have other OSes on this system and they are configured >>for the hardware clock set to local time. I need to keep it that way. > For what it's worth,

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-21 Thread Michael Stone
On Sun, May 20, 2018 at 12:15:05PM -0700, Patrick Bartek wrote: Unfortunately, I have other OSes on this system and they are configured for the hardware clock set to local time. I need to keep it that way. For what it's worth, you'll have less long term pain if you also configure those to use

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-21 Thread Greg Wooledge
On Sun, May 20, 2018 at 12:15:05PM -0700, Patrick Bartek wrote: > > > Haven't > > > installed any other OS on this system since Wheezy 5 years ago. Oh, good, then you can simply set the hardware cl-- > Unfortunately, I have other OSes on this system and they are configured > for the hardware

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-20 Thread Patrick Bartek
On Sun, 20 May 2018 22:42:24 +0300 Abdullah Ramazanoğlu wrote: > On Sun, 20 May 2018 12:10:01 -0700 Patrick Bartek said: > > > On Sat, 19 May 2018 03:52:27 +0300 Abdullah Ramazanoğlu > > wrote: > > > > > On Fri, 18 May 2018 17:13:07 -0700 Patrick Bartek said:

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-20 Thread Steve McIntyre
Patrick Bartek wrote: >On Fri, 18 May 2018 20:59:25 -0500 David Wright > wrote: > >> On Fri 18 May 2018 at 17:13:07 (-0700), Patrick Bartek wrote: >> > Okay, it's my fault: I admit it. During the Base Only, Terminal-only >> > install of Stretch, I clicked UTC instead of

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-20 Thread Abdullah Ramazanoğlu
On Sun, 20 May 2018 12:10:01 -0700 Patrick Bartek said: > On Sat, 19 May 2018 03:52:27 +0300 Abdullah Ramazanoğlu > wrote: > > > On Fri, 18 May 2018 17:13:07 -0700 Patrick Bartek said: > > > > > I could use hwclock --set --date= with the --localtime > > > option, etc., to

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-20 Thread Patrick Bartek
On Sat, 19 May 2018 10:37:39 +1000 Ben Finney wrote: > Patrick Bartek writes: > > > I could use hwclock --set --date= with the --localtime > > option, etc., to correct this but is there an easier way? > > There is only one clock involved in this: the

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-20 Thread Patrick Bartek
On Fri, 18 May 2018 20:59:25 -0500 David Wright wrote: > On Fri 18 May 2018 at 17:13:07 (-0700), Patrick Bartek wrote: > > Okay, it's my fault: I admit it. During the Base Only, Terminal-only > > install of Stretch, I clicked UTC instead of Local for the hardware > >

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-20 Thread Patrick Bartek
On Sat, 19 May 2018 03:52:27 +0300 Abdullah Ramazanoğlu wrote: > On Fri, 18 May 2018 17:13:07 -0700 Patrick Bartek said: > > > I could use hwclock --set --date= with the --localtime > > option, etc., to correct this but is there an easier way? > > # dpkg-reconfigure tzdata >

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-18 Thread David Wright
On Fri 18 May 2018 at 17:13:07 (-0700), Patrick Bartek wrote: > Okay, it's my fault: I admit it. During the Base Only, Terminal-only > install of Stretch, I clicked UTC instead of Local for the hardware > clock time. Honestly, I thought the clock was set to UTC. Haven't > installed any other OS on

Re: Correct: System Thinks Hardware Clock is UTC

2018-05-18 Thread Ben Finney
Patrick Bartek writes: > I could use hwclock --set --date= with the --localtime > option, etc., to correct this but is there an easier way? There is only one clock involved in this: the hardware clock. By telling the operating system that your hardware clock is set to UTC,

Correct: System Thinks Hardware Clock is UTC

2018-05-18 Thread Patrick Bartek
Okay, it's my fault: I admit it. During the Base Only, Terminal-only install of Stretch, I clicked UTC instead of Local for the hardware clock time. Honestly, I thought the clock was set to UTC. Haven't installed any other OS on this system since Wheezy 5 years ago. So, now system time on Stretch