freemint-discuss — The official FreeMiNT Mailing List

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

[Thorsten O. <ad...@th...>]

On Donnerstag, 9. August 2018 08:35:41 CEST David Gálvez wrote:
> . Macro TM_GTMOFF was not defined in the file
> tz/localtime.c use to build tzinit binary:

Argl, that's bad. Those macros are defined in the Makefile, and are supposed 
to be passed to all objects compiled in that directory, but it does not 
happen, because the objects are compiled by the top-level Makefile. In the 
current source archive, they are defined the private.h header file, so this 
couldn't happen.

Even worse, that does not only mean that tzinit does not work correctly, but 
the localtime() function in mintlib does not set the tm_gmtoff member.

Maybe that also explains the different behaviour in our setup, i'm sure that 
my tzinit version sets the gmtoff variable in the kernel, because i recently 
added debug output for it. 

But don't bother to fix this, i'm currently working on updating all that 
stuff. 

>"Time zone in use" output in tzinit is still null for me, it should be CEST.

Will hopefully be fixed then, too.

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

[David G. <dga...@gm...>]

2018-08-08 21:40 GMT+02:00 Peter Slegg <p....@sc...>:
> On Wed, 8 Aug 2018 08:59:59 , David Gálvez wrote:
>> Peter, where from and when did you get your tzinit?
>>
>
> I don't recall where it came from. Does this help ?
>
> tzinit - MiNTLib version 0.59.1
> Copyright (C) 1999 Guido Flohr <gu...@fr...>
> This program is free software, see the sources for copying conditions.
> There is no warranty, not even for merchantibility or fitness for a
> particular purpose.
>
> bash-4.3# ls -l /sbin/tzinit
> -rwxr-xr-x    1 root     root       108820 Jun  3  2010 /sbin/tzinit
>
>

It seems is from before the commit I pointed in a previous email, so
your issues are unrelated with what I'm seeing here.

While reading the tzinit sources I've seen that to set the kernel time
correctly we don't need to set /etc/localtime but
/usr/share/zoneinfo/localtime, my guess is that /etc/localtime is only
expected by some UNIX software. To set /usr/share/zoneinfo/localtime
you need the zic command, may be that localtime is not correctly set.
You could try to run this command and see if something changes:

zic -l Europe/London -p Europe/London

If nothing changes I'd wait until we fix the issues we're hitting and
I'd reinstall an up to date mintlib.

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

[David G. <dga...@gm...>]

2018-08-08 16:23 GMT+02:00 Thorsten Otto <ad...@th...>:
> On Mittwoch, 8. August 2018 12:28:33 CEST David Gálvez wrote:
>> This is with tzinit and a kernel fresh compiled from github sources,
>> running on Aranym with the option "GMTime" set.
>
> Your are right, seems to have to do with the setting of the GMTime option in
> aranym. Does not drift if i set it, and use tzinit -u instead. Hmm. Have to
> think about that again.
>

I can't replicate either the drift issue here if I unset GMTime in
Aranym and if I set the kernel in localtime mode, it must there be
still something different between our systems.
In the mean time I have found the reason why tzinit wasn't setting the
kernel timezone. Macro TM_GTMOFF was not defined in the file
tz/localtime.c use to build tzinit binary:

https://github.com/freemint/mintlib/blob/40caa38b3d4e5cd9dc1819e4d5e4e39de97618e0/tz/localtime.c#L1594

but it's defined for the other source files though:

https://github.com/freemint/mintlib/blob/40caa38b3d4e5cd9dc1819e4d5e4e39de97618e0/tz/Makefile#L45

I'm still thinking how to fix this nicely I'd like to avoid defining
TM_GTMOFF in two different places.

Besides the previous problems there are still some more things to fix:

root@aranym040:~> date
Thu Aug  9 08:25:00 CEST 2018

root@aranym040:~> tzinit
Current date and time: Thu Aug  9 08:25:04 2018
Time zone in use: (null)
East of Greenwich Mean Time: 2:00:00
Kernel clock mode: UTC

"Time zone in use" output in tzinit is still null for me, it should be CEST.

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

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

On Tue, 07 Aug 2018 19:07:33 , Thorsten Otto <ad...@th...> wrote:
> On Dienstag, 7. August 2018 18:07:10 CEST p....@sc... wrote:
> > It's the same issue, it never went away.
>
> But you failed to mention that. You also failed to mention that you are using
> a Milan with a modified BIOS. Instead, you let a few people try to hunt down
> bugs that apparently only exist in your (maybe broken) installation.
>
>

A few people have reported this issue but we were never able to isolate it.
The extra information was to help find the cause.

I haven't got a modifed BIOS.

Peter

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

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

On Wed, 8 Aug 2018 08:59:59 , David Gálvez wrote:
> I don't know yet if it's related with Peter's problem but some things
> got broken after this commit:
>
> https://github.com/freemint/mintlib/commit/e0ee0e7c5bd9709b15aec82417fb60633b1a7759#diff-2b58a42500d6e9196842792d186ce3d3
>
> tzinit built after that commit fails to set the kernel timezone
> correctly, it sets always the timezone offset to 0 regardless of the
> TZ environment variable value or the contents of the localtime file.
>
> Peter, where from and when did you get your tzinit?
>

I don't recall where it came from. Does this help ?

tzinit - MiNTLib version 0.59.1
Copyright (C) 1999 Guido Flohr <gu...@fr...>
This program is free software, see the sources for copying conditions.
There is no warranty, not even for merchantibility or fitness for a
particular purpose.

bash-4.3# ls -l /sbin/tzinit
-rwxr-xr-x    1 root     root       108820 Jun  3  2010 /sbin/tzinit


Peter

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

[Thorsten O. <ad...@th...>]

On Mittwoch, 8. August 2018 12:28:33 CEST David Gálvez wrote:
> This is with tzinit and a kernel fresh compiled from github sources,
> running on Aranym with the option "GMTime" set.

Your are right, seems to have to do with the setting of the GMTime option in 
aranym. Does not drift if i set it, and use tzinit -u instead. Hmm. Have to 
think about that again.

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

[David G. <dga...@gm...>]

2018-08-08 11:34 GMT+02:00 Thorsten Otto <ad...@th...>:
> On Mittwoch, 8. August 2018 08:59:59 CEST David Gálvez wrote:
>
>> tzinit built after that commit fails to set the kernel timezone
>
>> correctly,
>
>
>
> I cannot confirm that. My tzinit was built definitely after that commit, and
> it seems to set the timezone offset correctly. Only problem seems that it
> "drifts" when you repeatedly call it after booting:
>
>
>
> $ date
>
> Wed Aug  8 10:59:29 CEST 2018
>
> $ /sbin/tzinit -l
> Current date and time: Wed Aug  8 06:59:38 2018
> Time zone in use: CEST
> East of Greenwich Mean Time: 2:00:00
> Kernel clock mode: localtime
> $ /sbin/tzinit -l
> Current date and time: Wed Aug  8 02:59:40 2018
> Time zone in use: CEST
> East of Greenwich Mean Time: 2:00:00
> Kernel clock mode: localtime
> $ /sbin/tzinit -l
> Current date and time: Tue Aug  7 22:59:41 2018
> Time zone in use: CEST
> East of Greenwich Mean Time: 2:00:00
> Kernel clock mode: localtime
>
>
>
> etc.

I can't replicate your issues either, here the clock doesn't drift,
I've tested with "tzinit -l" and "tzinit -u".
This is with tzinit and a kernel fresh compiled from github sources,
running on Aranym with the option "GMTime" set.

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

[Thorsten O. <ad...@th...>]

On Mittwoch, 8. August 2018 08:59:59 CEST David Gálvez wrote:
> tzinit built after that commit fails to set the kernel timezone
> correctly,

I cannot confirm that. My tzinit was built definitely after that commit, and 
it seems to set the timezone offset correctly. Only problem seems that it 
"drifts" when you repeatedly call it after booting:

$ date
Wed Aug  8 10:59:29 CEST 2018 
$ /sbin/tzinit -l
Current date and time: Wed Aug  8 06:59:38 2018 
Time zone in use: CEST 
East of Greenwich Mean Time: 2:00:00 
Kernel clock mode: localtime 
$ /sbin/tzinit -l
Current date and time: Wed Aug  8 02:59:40 2018 
Time zone in use: CEST 
East of Greenwich Mean Time: 2:00:00 
Kernel clock mode: localtime 
$ /sbin/tzinit -l
Current date and time: Tue Aug  7 22:59:41 2018 
Time zone in use: CEST 
East of Greenwich Mean Time: 2:00:00 
Kernel clock mode: localtime

etc.

BTW updating the timezone database won't be that easy. The current version of 
the zic tool writes a timezone file that would not be understood by code 
compiled into older executables, so that would require recompiling all tools 
that make use of any of the time() functions. But it is about time, the 
current database only covers rules until ~2012

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

[David G. <dga...@gm...>]

I don't know yet if it's related with Peter's problem but some things
got broken after this commit:

https://github.com/freemint/mintlib/commit/e0ee0e7c5bd9709b15aec82417fb60633b1a7759#diff-2b58a42500d6e9196842792d186ce3d3

tzinit built after that commit fails to set the kernel timezone
correctly, it sets always the timezone offset to 0 regardless of the
TZ environment variable value or the contents of the localtime file.

Peter, where from and when did you get your tzinit?

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

[Thorsten O. <ad...@th...>]

On Dienstag, 7. August 2018 18:07:10 CEST p....@sc... wrote:
> It's the same issue, it never went away.

But you failed to mention that. You also failed to mention that you are using 
a Milan with a modified BIOS. Instead, you let a few people try to hunt down 
bugs that apparently only exist in your (maybe broken) installation.

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)

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

[Markus F. <mf...@mu...>]

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?

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

[Thorsten O. <ad...@th...>]

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.

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

[Paul W. <pau...@gm...>]

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
>

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

[Thorsten O. <ad...@th...>]

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.

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

[Paul W. <pau...@gm...>]

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
>

Re: [Freemint-discuss] Installation path for shared libs

[Paul W. <pau...@gm...>]

All the ARAnyM setups I have used are usually with MiNT and (loosely) based
around the (now old) AFROS CD fs structure. Of all the setups I have used,
only one had SLB placed anywhere but C:/mint/slb, and that was the French
created OpenGL enable ARAnyM + MiNT. I believe that was more to do with the
fact that they also develop with LDG, so theres were in C:/gemsys/slb next
to C:/gemsys/ldg.

As far as I understand it, MagiC's use of C:/gemsys/magix/extension is more
to do with the fact that the above where not in use yet (LDG and MiNT +
SLB), so there really was not a need for them to be anywhere else.

Although I would like to use MagiC with my drive setups, it not going to
happen in the foreseeable future. But I do use them in various
combinations, and what I found was that certain versions of SLB wont run on
certain setups. So I maintain a C:/mint/slb with 68020-060 and
C:/gemsys/slb for anything else, incl. 68000 (which is usually the only
other ones needed), next to C:/gemsys/ldg

Mikro is right tho, apart from ARAnyM & other Emu setups, on real HW there
is not even a need for what I've maintained, unless you are sharing a CF
card across different architectures, even then C: boot and auto needs to be
different anyway.

I believe some magic extensions cant be loaded if they are not in the
mention folder, hardcoded in a loader somewhere, but I dont remember what.

If you use MiNT, and require some (old) TOS apps to work, SLB's need to be
on C:, so C:/mint/slb covers both. If you share the fs with 68000 (or not
MiNT), then C:/gemsys/slb is safe for them, and it should work with Musashi
loaded 68000 on CF/FireBee as well.

If you only use specific hardware, but swap between MiNT and TOS boots, I
would still place the HW specific versions in C:/gemsys/slb, and 68020-060
in C:/mint/slb, at least you can easily share them with others, knowing
what architecture they are.

My 2cents worth

Paul


On Mon, Aug 6, 2018 at 2:51 AM, Thorsten Otto <ad...@th...> wrote:

> On Sonntag, 5. August 2018 13:52:47 CEST Miro Kropáček wrote:
> > applications like "setup.app" from various software packages (aniplayer
> > comes to my mind) simply copy all *.slb into given directory.
>
> Yes, but having a to write a "setup.app" would be extra effort. Also i'm
> currently speaking about more standard libraries like zlib and pnglib that
> are
> not specific to a single application (i just wonder that apparently nobody
> has
> built such things yet).
>
> >To make this totally right I'd say FreeMiNT would need to look after
> >$SLBPATH/$CPU in addition to just $SLBPATH, very similar what
> mintloader.prg
> >does for freemint modules ($SYSDIR + $SYSDIR/<machine specific folder>).
>
> That would make sense. But of course that currently does not help much
> currently as long as this is not implemented.
>
>
>
> ------------------------------------------------------------
> ------------------
> 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
>

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

[David G. <dga...@gm...>]

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.

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

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

On Sun, 05 Aug 2018 20:40:31 , Helmut Karlowski via Freemint-discuss <fre...@li...> wrote:
> Am 05.08.2018, 20:08 Uhr, schrieb Helmut Karlowski:
>
> > 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
>
> With TZ unset I get:
>
> unset TZ
> 708¦/charts}/c/mint/tzinit
> tzinit: do_utc=0,do_local=0
> tzload: name=(null),TZDIR=/usr/share/zoneinfo
> tzload: access name=/usr/share/zoneinfo/localtime
> tzload: open name=/usr/share/zoneinfo/localtime
> tzload: nread=2789
> localsub: timesub,tt_gmtoff=7200,tt_abbrind=0,chars='CEST'
> Current date and time: Sun Aug  5 21:37:53 2018
> Time zone in use: CEST
> East of Greenwich Mean Time: 2:00:00
> Kernel clock mode: localtime
>
> which seems to prove my point ...
>
> -Helmut
>

You lost me. Not sure what you are trying to illustrate.

Peter

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

[Helmut K. <hel...@is...>]

Am 05.08.2018, 20:08 Uhr, schrieb Helmut Karlowski:

> 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

With TZ unset I get:

unset TZ
708|/charts}/c/mint/tzinit
tzinit: do_utc=0,do_local=0
tzload: name=(null),TZDIR=/usr/share/zoneinfo
tzload: access name=/usr/share/zoneinfo/localtime
tzload: open name=/usr/share/zoneinfo/localtime
tzload: nread=2789
localsub: timesub,tt_gmtoff=7200,tt_abbrind=0,chars='CEST'
Current date and time: Sun Aug  5 21:37:53 2018
Time zone in use: CEST
East of Greenwich Mean Time: 2:00:00
Kernel clock mode: localtime

which seems to prove my point ...

-Helmut


--

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

[Helmut K. <hel...@is...>]

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

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

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

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

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

[David G. <dga...@gm...>]

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.

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

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

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

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

[Thorsten O. <ad...@th...>]

Works as expected here (Europe/Berlin is my actual local timezone):

$ echo $TZ

$ rm -f /etc/localtime
$ cp /usr/share/zoneinfo/Factory /etc/localtime
$ date
Sun Aug  5 17:21:39 Local time zone must be set--see zic manual page 2018
$ cp /usr/share/zoneinfo/Europe/London /etc/localtime
$ date
Sun Aug  5 18:22:12 BST 2018
$ cp /usr/share/zoneinfo/Europe/Berlin /etc/localtime
$ date
Sun Aug  5 19:22:23 CEST 2018
$ /sbin/tzinit -l
Current date and time: Sat Aug  4 11:22:40 2018 
Time zone in use: CEST 
East of Greenwich Mean Time: 2:00:00 
Kernel clock mode: localtime


Note that the date printed from the tzinit call is bogus. That is because you 
must not execute it at runtime, only once from mint.cnf. But everything else 
(timezone name, and GMT offset) should be correct.

I also prefer to use --localtime, because that is what non-mint-aware programs 
will expect when calling Tgettime().