Re: [Freemint-discuss] Fwd: Re: Timezone and timestamp

[<p....@sc...>]

It's the same issue, it never went away.

Someone else also reported issues a few years ago. I am not sure which
mailing archive it will be on

Peter

---- Original Message ----
From: Paul Wratt 
To: "freemint-discuss" 
Sent: Tue, Aug 7, 2018, 6:25 AM
Subject: Re: [Freemint-discuss] Fwd: Re: Timezone and timestamp
This not the first, or even the third time Peter has had issues with
TZ/timezone and remote fs dates.

One major difference between setups is he is using a Milan. Does anyone
else with a Milan use MiNT (is it 040 or 060)?

Second, I know that his original configs cam from a different setup, is
there an issue there, something being missed (like was edited under TOS and
under MiNT "tzload" is having issues with it).

Third, where is his tzinit coming from, 1.15, 1.16, 1.17, 1.18,
1.19-current. I know there have been issues with certain combinations on
certain architecture in the past (like a long time ago as well).

every now and again I have issues with "plain text" files not being
processed properly. Usually config or Makefile's, and it is always either
the file was also edited on non-linux, I pasted a unseeable (control?)
character. whatever it is, I usually have to remove the EOL + 1 character
either side of it, and it usually fixes the issue. Just an idea ..

on that note, if this continues, wont it be easier to copy/share a 020-060
tzinit and timezone files from a known working source.

Cheers

Paul

On Mon, Aug 6, 2018 at 8:07 AM, David Gálvez  wrote:
2018-08-05 22:07 GMT+02:00 Peter Slegg :
 >
 > I rebooted into TOS but it doesn't load any ACCS so I cannot set the
clock.
 >
 > So I set the clock in Xboot but when I got back into Mint it was 1hr too
early again.
 >
 > There is only tzinit left so I ran it repeatedly. It puts the clock back
1 hr each time.
 >
 > Thorsten said not to run it from bash, that may explain the odd
behaviour.
 >
 >
 > bash-4.3# date
 > Sun Aug  5 16:59:57 BST 2018
 >
 > bash-4.3# /sbin/tzinit -u
 > Current date and time: Sun Aug  5 17:00:02 2018
 > Time zone in use: BST
 > East of Greenwich Mean Time: 1:00:00
 > Kernel clock mode: UTC
 > bash-4.3# date
 > Sun Aug  5 17:00:04 BST 2018
 >
 > bash-4.3# /sbin/tzinit -l
 > Current date and time: Sun Aug  5 16:00:08 2018
 > Time zone in use: BST
 > East of Greenwich Mean Time: 1:00:00
 > Kernel clock mode: localtime
 > bash-4.3# date
 > Sun Aug  5 16:00:17 BST 2018
 >
 > bash-4.3# /sbin/tzinit -u
 > Current date and time: Sun Aug  5 15:00:22 2018
 > Time zone in use: BST
 > East of Greenwich Mean Time: 1:00:00
 > Kernel clock mode: UTC
 > bash-4.3# date
 > Sun Aug  5 15:00:25 BST 2018
 >
 > bash-4.3# /sbin/tzinit -l
 > Current date and time: Sun Aug  5 14:00:37 2018
 > Time zone in use: BST
 > East of Greenwich Mean Time: 1:00:00
 > Kernel clock mode: localtime
 > bash-4.3# date
 > Sun Aug  5 14:00:40 BST 2018
 >
 Weird. I need time to investigate this. It should work, on my Falcon
 is working fine, I get the correct time and the right timestamps for
 files from the desktop or command lines tools with kernel set to UTC
 mode.
 As soon as I find something I'll report back.
 ------------------------------------------------------------------------------
 Check out the vibrant tech community on one of the world's most
 engaging tech sites, Slashdot.org! http://sdm.link/slashdot
(http://sdm.link/slashdot)
 _______________________________________________
 Freemint-discuss mailing list
 Fre...@li...
(mailto:Fre...@li...)
 https://lists.sourceforge.net/lists/listinfo/freemint-discuss
(https://lists.sourceforge.net/lists/listinfo/freemint-discuss)