|
From: Peter S. <p....@sc...> - 2018-07-29 12:19:19
|
2018-07-29 11:23 GMT+02:00 David GÃílvez <dga...@gm...>: > Do you have the timezone data base installed?, see if you have the > file /etc/localtime in your system, if so you don't need to set the > system variable TZ in mint.cnf, but be aware that the file localtime > must be the correct one for you time zone. If not you can copy it from > /usr/share/zoneinfo to the /etc directory and rename it to > "localtime". >Sorry, possibly this is not the way to install your localtime file, my >memory failed me again. The "zic" command should be used instead, read >this: >https://github.com/freemint/mintlib/blob/master/tz/README.1st - The localtime file is a link to /usr/share/zoneinfo/factory which contains: TZif 1 Local time zone must be set--see zic manual page Peter |
|
From: Peter S. <p....@sc...> - 2018-07-29 12:23:12
|
On Sun, 29 Jul 2018 12:19:10 , Peter Slegg <p....@sc...> wrote: > > > 2018-07-29 11:23 GMT+02:00 David GÃílvez <dga...@gm...>: > > Do you have the timezone data base installed?, see if you have the > > file /etc/localtime in your system, if so you don't need to set the > > system variable TZ in mint.cnf, but be aware that the file localtime > > must be the correct one for you time zone. If not you can copy it from > > /usr/share/zoneinfo to the /etc directory and rename it to > > "localtime". > > >Sorry, possibly this is not the way to install your localtime file, my > >memory failed me again. The "zic" command should be used instead, read > >this: > >https://github.com/freemint/mintlib/blob/master/tz/README.1st > > - > > The localtime file is a link to /usr/share/zoneinfo/factory which > contains: > > TZif 1 Local time zone mus > t be set--see zic manual page > > > > Peter > This looks wrong: bash-4.3# tzinit Current date and time: Sun Jul 29 12:18:04 2018 Time zone in use: BST East of Greenwich Mean Time: 1:00:00 Kernel clock mode: localtime bash-4.3# date Sun Jul 29 12:18:07 BST 2018 |
|
From: Thorsten O. <ad...@th...> - 2018-07-29 14:23:32
|
On Sonntag, 29. Juli 2018 14:23:01 CEST Peter Slegg wrote: > bash-4.3# tzinit > Current date and time: Sun Jul 29 12:18:04 2018 > Time zone in use: BST > East of Greenwich Mean Time: 1:00:00 > Kernel clock mode: localtime > bash-4.3# date > Sun Jul 29 12:18:07 BST 2018 That looks indeed wrong, it is still using the "Factory" defaults. It should look like this: Current date and time: Sun Jul 29 16:20:24 2018 Time zone in use: CEST East of Greenwich Mean Time: 2:00:00 Kernel clock mode: localtime |
|
From: David G. <dga...@gm...> - 2018-07-29 14:55:47
|
2018-07-29 14:23 GMT+02:00 Peter Slegg <p....@sc...>: > > > This looks wrong: > > bash-4.3# tzinit > Current date and time: Sun Jul 29 12:18:04 2018 > Time zone in use: BST > East of Greenwich Mean Time: 1:00:00 > Kernel clock mode: localtime > bash-4.3# date > Sun Jul 29 12:18:07 BST 2018 > The kernel is still in localtime mode. Did you edit the tzinit option from "-l" to "-u" in mint.cnf? |
|
From: Peter S. <p....@sc...> - 2018-07-29 15:21:54
|
On Sun, 29 Jul 2018 16:55:39 , David Gálvez wrote: > 2018-07-29 14:23 GMT+02:00 Peter Slegg <p....@sc...>: > > > > > > This looks wrong: > > > > bash-4.3# tzinit > > Current date and time: Sun Jul 29 12:18:04 2018 > > Time zone in use: BST > > East of Greenwich Mean Time: 1:00:00 > > Kernel clock mode: localtime > > bash-4.3# date > > Sun Jul 29 12:18:07 BST 2018 > > > > The kernel is still in localtime mode. Did you edit the tzinit option > from "-l" to "-u" in mint.cnf? > No, that was without any changes. Changing it to -u and rebooting: bash-4.3# tzinit Current date and time: Sun Jul 29 15:18:25 2018 Time zone in use: BST East of Greenwich Mean Time: 1:00:00 Kernel clock mode: UTC bash-4.3# date Sun Jul 29 15:18:32 BST 2018 It is currently 16:18 BST Peter |
|
From: David G. <dga...@gm...> - 2018-07-29 15:41:55
|
2018-07-29 17:21 GMT+02:00 Peter Slegg <p....@sc...>: > On Sun, 29 Jul 2018 16:55:39 , David Gálvez wrote: >> >> The kernel is still in localtime mode. Did you edit the tzinit option >> from "-l" to "-u" in mint.cnf? >> > > No, that was without any changes. > > Changing it to -u and rebooting: > > bash-4.3# tzinit > Current date and time: Sun Jul 29 15:18:25 2018 > Time zone in use: BST > East of Greenwich Mean Time: 1:00:00 > Kernel clock mode: UTC > > bash-4.3# date > Sun Jul 29 15:18:32 BST 2018 > > > It is currently 16:18 BST > > It's very strange, are you sure the ntpdate command is getting the time from the server successfully at boot? |
|
From: Peter S. <p....@sc...> - 2018-08-04 20:52:36
|
On Sun, 29 Jul 2018 17:41:47 , David Gálvez wrote: 2018-07-29 17:21 GMT+02:00 Peter Slegg <p....@sc...>: > On Sun, 29 Jul 2018 16:55:39 , David GÃílvez wrote: >> >> The kernel is still in localtime mode. Did you edit the tzinit option >> from "-l" to "-u" in mint.cnf? >> > > No, that was without any changes. > > Changing it to -u and rebooting: > > bash-4.3# tzinit > Current date and time: Sun Jul 29 15:18:25 2018 > Time zone in use: BST > East of Greenwich Mean Time: 1:00:00 > Kernel clock mode: UTC > > bash-4.3# date > Sun Jul 29 15:18:32 BST 2018 > > > It is currently 16:18 BST > > It's very strange, are you sure the ntpdate command is getting the time from the server successfully at boot? -- I did have ntpdate in mint.cnf but it seems to have gone from the mint.cnf files in all the folders ! Last year I was trying to get ntpd working, so maybe I removed it then. I have put ntpdate back again. # Timezone (mandatory) #~setenv TZ GMT-0BST,3.5.0,10.5.0 setenv TZ GB #exec u:\sbin\tzinit -l exec u:\sbin\tzinit -u ntpdate pool.ntp.org Peter |
|
From: David G. <dga...@gm...> - 2018-08-05 08:59:54
|
2018-08-04 22:52 GMT+02:00 Peter Slegg <p....@sc...>: > I did have ntpdate in mint.cnf but it seems to have gone from the > mint.cnf files in all the folders ! > > Last year I was trying to get ntpd working, so maybe I removed it then. > > I have put ntpdate back again. > > # Timezone (mandatory) > #~setenv TZ GMT-0BST,3.5.0,10.5.0 > setenv TZ GB > #exec u:\sbin\tzinit -l > exec u:\sbin\tzinit -u > ntpdate pool.ntp.org > Do you have now the right time? |
|
From: Peter S. <p....@sc...> - 2018-08-05 14:47:36
|
On Sun, 5 Aug 2018 10:59:46 , David Gálvez wrote: > 2018-08-04 22:52 GMT+02:00 Peter Slegg <p....@sc...>: > > I did have ntpdate in mint.cnf but it seems to have gone from the > > mint.cnf files in all the folders ! > > > > Last year I was trying to get ntpd working, so maybe I removed it then. > > > > I have put ntpdate back again. > > > > # Timezone (mandatory) > > #~setenv TZ GMT-0BST,3.5.0,10.5.0 > > setenv TZ GB > > #exec u:\sbin\tzinit -l > > exec u:\sbin\tzinit -u > > ntpdate pool.ntp.org > > > > Do you have now the right time? > No, it's still showing GMT when I think it should be showing BST. I assume TZ GB should alter the time on the correct date ? Peter |
|
From: Thorsten O. <ad...@th...> - 2018-08-05 14:54:26
|
On Sonntag, 5. August 2018 16:47:23 CEST Peter Slegg wrote: > I assume TZ GB should alter the time on the correct date ? tzinit does not care about the TZ environment variable. You have to copy or link the correct file from /usr/share/zoneinfo/* to /etc/localtime |
|
From: Peter S. <p....@sc...> - 2018-08-05 15:31:20
|
On Sun, 05 Aug 2018 16:54:17 , Thorsten Otto <ad...@th...> wrote: > On Sonntag, 5. August 2018 16:47:23 CEST Peter Slegg wrote: > > I assume TZ GB should alter the time on the correct date ? > > tzinit does not care about the TZ environment variable. You have to copy or > link the correct file from /usr/share/zoneinfo/* to /etc/localtime > > The localtime file is a link lrwxrwxrwx 1 root root 29 May 1 2016 localtime -> /usr/share/zoneinfo/Factory Peter |
|
From: Peter S. <p....@sc...> - 2018-08-05 16:27:28
|
On Sun, 5 Aug 2018 15:31:10 , Peter Slegg <p....@sc...> wrote: > On Sun, 05 Aug 2018 16:54:17 , Thorsten Otto <ad...@th...> wrote: > > On Sonntag, 5. August 2018 16:47:23 CEST Peter Slegg wrote: > > > I assume TZ GB should alter the time on the correct date ? > > > > tzinit does not care about the TZ environment variable. You have to copy or > > link the correct file from /usr/share/zoneinfo/* to /etc/localtime > > > > > > > The localtime file is a link > > lrwxrwxrwx 1 root root 29 May 1 2016 localtime -> /usr/share/zoneinfo/Factory > > > Peter > I changed the link to use London but it is still shoiwng GMT time bash-4.3# date Sun Aug 5 15:43:02 BST 2018 What is TZ for ? Peter |
|
From: Thorsten O. <ad...@th...> - 2018-08-05 16:34:23
|
On Sonntag, 5. August 2018 18:27:17 CEST Peter Slegg wrote: > What is TZ for ? TZ is for older libraries like the one from PureC that don't have a timezone database. |
|
From: Peter S. <p....@sc...> - 2018-08-05 16:55:01
|
On Sun, 05 Aug 2018 18:34:13 , Thorsten Otto <ad...@th...> wrote: > On Sonntag, 5. August 2018 18:27:17 CEST Peter Slegg wrote: > > What is TZ for ? > > TZ is for older libraries like the one from PureC that don't have a timezone > database. > > Thanks. I had assumed it was for tzinit. I tried calling ntpdate before tzinit but it still shows GMT. So from bash I tried various combinations. The time is currently 17:50 BST but it only shows 16:50 or 15:50 Test with tzinit -u bash-4.3# date Sun Aug 5 16:51:27 BST 2018 bash-4.3# ntpdate pool.ntp.org Looking for host pool.ntp.org and service ntp host found : fluffykins.positive-internet.com 5 Aug 16:51:32 ntpdate[205]: step time server 80.87.128.222 offset 3600.563846 sec bash-4.3# date Sun Aug 5 16:51:34 BST 2018 bash-4.3# /sbin/tzinit -u Current date and time: Sun Aug 5 16:51:41 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 16:51:42 BST 2018 Test with tzinit -l bash-4.3# date Sun Aug 5 16:52:27 BST 2018 bash-4.3# /sbin/tzinit -l Current date and time: Sun Aug 5 15:52:39 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 15:52:46 BST 2018 bash-4.3# ntpdate pool.ntp.org Looking for host pool.ntp.org and service ntp host found : time.rdg.uk.as44574.net 5 Aug 16:52:52 ntpdate[212]: step time server 193.150.34.2 offset 7200.727898 sec bash-4.3# date Sun Aug 5 16:52:54 BST 2018 Peter |
|
From: David G. <dga...@gm...> - 2018-08-05 17:16:52
|
2018-08-05 18:54 GMT+02:00 Peter Slegg <p....@sc...>: > Thanks. I had assumed it was for tzinit. > > I tried calling ntpdate before tzinit but it still shows GMT. > > So from bash I tried various combinations. > The time is currently 17:50 BST but it only shows 16:50 or 15:50 > > > Test with tzinit -u > > bash-4.3# date > Sun Aug 5 16:51:27 BST 2018 > > bash-4.3# ntpdate pool.ntp.org > Looking for host pool.ntp.org and service ntp > host found : fluffykins.positive-internet.com > 5 Aug 16:51:32 ntpdate[205]: step time server 80.87.128.222 offset 3600.563846 sec > > bash-4.3# date > Sun Aug 5 16:51:34 BST 2018 > > bash-4.3# /sbin/tzinit -u > Current date and time: Sun Aug 5 16:51:41 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 16:51:42 BST 2018 > > > > Test with tzinit -l > > bash-4.3# date > Sun Aug 5 16:52:27 BST 2018 > > bash-4.3# /sbin/tzinit -l > Current date and time: Sun Aug 5 15:52:39 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 15:52:46 BST 2018 > > bash-4.3# ntpdate pool.ntp.org > Looking for host pool.ntp.org and service ntp > host found : time.rdg.uk.as44574.net > 5 Aug 16:52:52 ntpdate[212]: step time server 193.150.34.2 offset 7200.727898 sec > > bash-4.3# date > Sun Aug 5 16:52:54 BST 2018 > Can you comment/remove the line where TZ variable is set in mint.cnf and try again? Show us please the output of date, tzinit and ntpdate after the variable is unset. |
|
From: Peter S. <p....@sc...> - 2018-08-05 17:54:08
|
On Sun, 5 Aug 2018 19:16:44 , David Gálvez wrote: > 2018-08-05 18:54 GMT+02:00 Peter Slegg <p....@sc...>: > > Thanks. I had assumed it was for tzinit. > > > > I tried calling ntpdate before tzinit but it still shows GMT. > > > > So from bash I tried various combinations. > > The time is currently 17:50 BST but it only shows 16:50 or 15:50 > > > > > > Test with tzinit -u > > > > bash-4.3# date > > Sun Aug 5 16:51:27 BST 2018 > > > > bash-4.3# ntpdate pool.ntp.org > > Looking for host pool.ntp.org and service ntp > > host found : fluffykins.positive-internet.com > > 5 Aug 16:51:32 ntpdate[205]: step time server 80.87.128.222 offset 3600.563846 sec > > > > bash-4.3# date > > Sun Aug 5 16:51:34 BST 2018 > > > > bash-4.3# /sbin/tzinit -u > > Current date and time: Sun Aug 5 16:51:41 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 16:51:42 BST 2018 > > > > > > > > Test with tzinit -l > > > > bash-4.3# date > > Sun Aug 5 16:52:27 BST 2018 > > > > bash-4.3# /sbin/tzinit -l > > Current date and time: Sun Aug 5 15:52:39 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 15:52:46 BST 2018 > > > > bash-4.3# ntpdate pool.ntp.org > > Looking for host pool.ntp.org and service ntp > > host found : time.rdg.uk.as44574.net > > 5 Aug 16:52:52 ntpdate[212]: step time server 193.150.34.2 offset 7200.727898 sec > > > > bash-4.3# date > > Sun Aug 5 16:52:54 BST 2018 > > > > Can you comment/remove the line where TZ variable is set in mint.cnf > and try again? > Show us please the output of date, tzinit and ntpdate after the > variable is unset. > It is currently 17:48 GMT, 18:48 BST London is GMT. BST is 1hr East of GMT (GMT +1hr) bash-4.3# ntpdate pool.ntp.org Looking for host pool.ntp.org and service ntp host found : babbage.betadome.net 5 Aug 17:48:40 ntpdate[160]: step time server 109.74.192.233 offset 3600.768161 sec bash-4.3# date Sun Aug 5 17:48:42 BST 2018 bash-4.3# /sbin/tzinit -u Current date and time: Sun Aug 5 17:48:59 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:49:01 BST 2018 bash-4.3# /sbin/tzinit -l Current date and time: Sun Aug 5 16:49:05 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:49:08 BST 2018 bash-4.3# ntpdate pool.ntp.org Looking for host pool.ntp.org and service ntp host found : time.netweaver.uk 5 Aug 17:49:18 ntpdate[166]: step time server 185.182.62.7 offset 7201.144011 sec bash-4.3# date Sun Aug 5 17:49:22 BST 2018 |
|
From: David G. <dga...@gm...> - 2018-08-05 18:25:12
|
2018-08-05 19:53 GMT+02:00 Peter Slegg <p....@sc...>: > > It is currently 17:48 GMT, 18:48 BST > > London is GMT. BST is 1hr East of GMT (GMT +1hr) > > > > > bash-4.3# ntpdate pool.ntp.org > Looking for host pool.ntp.org and service ntp > host found : babbage.betadome.net > 5 Aug 17:48:40 ntpdate[160]: step time server 109.74.192.233 offset 3600.768161 sec > > bash-4.3# date > Sun Aug 5 17:48:42 BST 2018 > > bash-4.3# /sbin/tzinit -u > Current date and time: Sun Aug 5 17:48:59 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:49:01 BST 2018 > > bash-4.3# /sbin/tzinit -l > Current date and time: Sun Aug 5 16:49:05 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:49:08 BST 2018 > > bash-4.3# ntpdate pool.ntp.org > Looking for host pool.ntp.org and service ntp > host found : time.netweaver.uk > 5 Aug 17:49:18 ntpdate[166]: step time server 185.182.62.7 offset 7201.144011 sec > > bash-4.3# date > Sun Aug 5 17:49:22 BST 2018 > Very strange, I can't figure out the problem in your system, I need to investigate this further. I want to see ntpdate sources because I don't understand what it's doing. For now I'd simplify things, I'd forget about ntp and I'd try to make it work only with the hardware clock. I'd go into TOS and see what is the time the hardware clock is ticking from there (I have the feeling is set to GMT-1), I'd set it to UTC/GMT and I'd try again with MiNT, I'd keep TZ unset and I'd start "tzinit -u" from mint.cnf. |
|
From: Peter S. <p....@sc...> - 2018-08-05 19:08:48
|
On Sun, 5 Aug 2018 20:25:04 , David Gálvez wrote: > 17:49:22 BST 2018 > > > > Very strange, I can't figure out the problem in your system, I need to > investigate this further. I want to see ntpdate sources because I > don't understand what it's doing. > For now I'd simplify things, I'd forget about ntp and I'd try to make > it work only with the hardware clock. I'd go into TOS and see what is > the time the hardware clock is ticking from there (I have the feeling > is set to GMT-1), I'd set it to UTC/GMT and I'd try again with MiNT, > I'd keep TZ unset and I'd start "tzinit -u" from mint.cnf. > 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 Peter |
|
From: David G. <dga...@gm...> - 2018-08-05 20:07:34
|
2018-08-05 22:07 GMT+02:00 Peter Slegg <p....@sc...>: > > 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. |
|
From: Paul W. <pau...@gm...> - 2018-08-07 05:24:56
|
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 <dga...@gm...> wrote: > 2018-08-05 22:07 GMT+02:00 Peter Slegg <p....@sc...>: > > > > 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 > _______________________________________________ > Freemint-discuss mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemint-discuss > |
|
From: Markus F. <mf...@mu...> - 2018-08-07 06:43:37
|
Am 07.08.2018 um 07:24 schrieb Paul Wratt: > One major difference between setups is he is using a Milan. Does > anyone else with a Milan use MiNT (is it 040 or 060)? > FreMiNT Tsettimeofday() eventually calls the ROM Settime() function internally. If the Milan TOS Settime() function behaves differently from "normal" TOS time handling, this could perhaps explain it? |
|
From: Thorsten O. <ad...@th...> - 2018-08-07 05:39:32
|
On Dienstag, 7. August 2018 07:24:46 CEST Paul Wratt wrote: > 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. This is actually a major issue. First off, the current timezone database in mintlib is a bit outdated. But most importantly: with our current cross- compilation setup, it cannot easily be build automatically. You (obviously) cannot use the just build executables for that, and it is also very difficult to compile them by the native host compiler in a way that the generated executables (zic mainly) produce files that are then usable by the target system afterwards. Also there might be mismatches with pathnames from the host and the target, some of them are compiled in. |
|
From: Paul W. <pau...@gm...> - 2018-08-07 05:49:37
|
isnt it possible to rebuild the ones from SRPM from SpareMiNT, patched with the new db files and any fixes that are not too much out of the way. This might require using gcc 2.xx to do so (since that what was use successfully originally) Alternatively, what about using the src's from GentooMiNT, and cross-compile those for an update On Tue, Aug 7, 2018 at 5:39 PM, Thorsten Otto <ad...@th...> wrote: > On Dienstag, 7. August 2018 07:24:46 CEST Paul Wratt wrote: > > 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. > > This is actually a major issue. First off, the current timezone database > in > mintlib is a bit outdated. But most importantly: with our current cross- > compilation setup, it cannot easily be build automatically. You > (obviously) > cannot use the just build executables for that, and it is also very > difficult > to compile them by the native host compiler in a way that the generated > executables (zic mainly) produce files that are then usable by the target > system afterwards. Also there might be mismatches with pathnames from the > host > and the target, some of them are compiled in. > > > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Freemint-discuss mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemint-discuss > |
|
From: Thorsten O. <ad...@th...> - 2018-08-07 06:24:43
|
On Dienstag, 7. August 2018 07:49:28 CEST Paul Wratt wrote: > Alternatively, what about using the src's from GentooMiNT, and cross-compile > those for an update That's not the problem, the sources are in the mintlib repo (in the tz subdirectory). But the actual files that are installed in /usr/share/zoneinfo are machine-dependent files that are generated by zic. You will have to cross- compile zic, then take the executable and all those description files, transfer it to a real machine (or emulator), run it there using the commands from the original makefile, install them, and then transfer the generated files back. Also, using any files from GenToo would be actually a downgrade, since they are much older. |
|
From: Helmut K. <hel...@is...> - 2018-08-05 19:22:10
|
Am 05.08.2018, 19:25 Uhr, schrieb David Gálvez: > Very strange, I can't figure out the problem in your system, I need to As far as I understand it /usr/share/zoneinfo/localtime has to be a copy of or link to your timezone-file (in your case /usr/share/zoneinfo/Europe/London). That's how it works for me (on aranym). I seem to have had issues with tzinit too, and now it outputs some debue-messages: #/c/mint/tzinit tzinit: do_utc=0,do_local=0 tzset: name=Europe/Berlin tzload: name=Europe/Berlin,TZDIR=/usr/share/zoneinfo tzload: access name=/usr/share/zoneinfo/Europe/Berlin tzload: open name=/usr/share/zoneinfo/Europe/Berlin tzload: nread=2789 localsub: timesub,tt_gmtoff=7200,tt_abbrind=0,chars='CEST' tzset: name=Europe/Berlin Current date and time: Sun Aug 5 21:02:26 2018 Time zone in use: CEST East of Greenwich Mean Time: 2:00:00 Kernel clock mode: localtime Don't know if I changed something else in tzinit. Don't call tzinit -l - it sets a wrong time. I also have TZ=Europe/Berlin TZDIR=/usr/share/zoneinfo TZDIST=2 in the environment, don't know if it's necessary. -Helmut |