Hi there,
I while back I checked and looked as if slackware knew DST changes
later this year in Aus... Not so Here I am with deltree (slackware,
ntp sync to UTC) saying +1000 -- wrong, but the winxp box hangin off of
it correctly giving +1100 matching the house 'standard', a battery
operated clock.

Grrr. Couple weeks of madness. Another slack f'up.

Grant.
--
WinXP: Access Start->Turn Off Computer, then while holding Ctrl-Alt-Shift,
left click on Cancel. This terminates Windows Explorer...

Hi there,

Trick is, one needs to copy /usr/share/zoneinfo/Australia/Victoria (in
my case) to /etc/localtime... So why isn't /etc/localtime a symlink
in the first place?

Very odd, now visit half a dozen other linux boxen and fix? Yup

Grant.
--
WinXP: Access Start->Turn Off Computer, then while holding Ctrl-Alt-Shift,
left click on Cancel. This terminates Windows Explorer...

On 2006-03-26, Grant <bugsplatter@gmail.com> wrote:
> Hi there,
>
> Trick is, one needs to copy /usr/share/zoneinfo/Australia/Victoria (in
> my case) to /etc/localtime... So why isn't /etc/localtime a symlink
> in the first place?
>
> Very odd, now visit half a dozen other linux boxen and fix? Yup
>
> Grant.

It is on my box, well, not to Aus/Victoria but still symlink to
/usr/share/zoneinfo/US/Eastern

Odd is, you're the one that told me about it within the last two
weeks.....right??? I said it was a binary, I think, you said it was a ....


ken

On Sun, 26 Mar 2006 00:58:20 GMT, No_One <no_one@no_where.com> wrote:

>On 2006-03-26, Grant <bugsplatter@gmail.com> wrote:
>> Hi there,
>>
>> Trick is, one needs to copy /usr/share/zoneinfo/Australia/Victoria (in
>> my case) to /etc/localtime... So why isn't /etc/localtime a symlink
>> in the first place?
>>
>> Very odd, now visit half a dozen other linux boxen and fix? Yup
>>
>> Grant.
>
>It is on my box, well, not to Aus/Victoria but still symlink to
>/usr/share/zoneinfo/US/Eastern
>
>Odd is, you're the one that told me about it within the last two
>weeks.....right??? I said it was a binary, I think, you said it was a ....

Few weeks back I discovered our crazy Govt. changed DST for Commonwealth
Games, but at the time it looked as if slackware already had the fix
since /usr/share/zoneinfo/* was dated Sep'05, after the new timezones
were announced, I think only Stan. Flatto responded to that one...

So this morning I have wrong time, and, on investigation find that
copying slack-current usr/share/zoneinfo/Australia/Victoria to
/etc/localtime worked, but the slack-current files are stamped Feb'06.


It's a binary file, I remember some related discussion about a missing
(for some of us) /etc/timezone file, which I don't have -- that (I think)
was the most recent discussion.

Odd thing was another slack (10.1 or .2) box got knocked back from +1100
to +1000 on startup (localtime in RTC), so I had to copy the file to it.

The laptop was 7200 seconds out -- not even hazard a guess what happened
there as its running local time in RTC too for dual boot win98 + win2k...

That's three down five to go, but the rest also need a network ID change
too, one is a reinstall 'cos I swapped HDDs -- we expecting 31'C here
today -- too warm to run lots of PCs like I do in winter-time.

Grant.
--
WinXP: Access Start->Turn Off Computer, then while holding Ctrl-Alt-Shift,
left click on Cancel. This terminates Windows Explorer...

Grant wrote:
> I while back I checked and looked as if slackware knew DST changes
> later this year in Aus... Not so Here I am with deltree (slackware,
> ntp sync to UTC) saying +1000 -- wrong, but the winxp box hangin off of
> it correctly giving +1100 matching the house 'standard', a battery
> operated clock.
>
> Grrr. Couple weeks of madness. Another slack f'up.

Grant, I don't have an answer to your post but an info.

I am having two Slackware-current machines with almost identical
configuration. Both have an /etc/localtime file and a symlink
/etc/localtime-copied-from . The main difference between the machines
is that one of them is running 24/7 while the other one is up only for
a few hours a day. The point is that the "24/7" machine updated its
clock but the other one did not. Perhaps, one should run Slack 24/7
:-)

--
Mikhail

On 27 Mar 2006 11:54:32 -0800, "Mikhail Zotov" <muxaul@lenta.ru> wrote:

>Grant, I don't have an answer to your post but an info.
>
>I am having two Slackware-current machines with almost identical
>configuration. Both have an /etc/localtime file and a symlink
>/etc/localtime-copied-from . The main difference between the machines
>is that one of them is running 24/7 while the other one is up only for
>a few hours a day. The point is that the "24/7" machine updated its
>clock but the other one did not. Perhaps, one should run Slack 24/7
>:-)

Not the issue, we (the land downunder) just hosted Commonwealth Games
and 'they' (the Govt.) decided to delay DST turnoff for a week. But
slackware's 10.2 had the old DST timing, even though the file was dated
Sep'05.

Solution was to copy slack-current's timezone info over. This is
a one-off issue affecting Eastern Australian States for a week...

Firewall is up 24/7 and is ntp synchronised, the problem is the other
boxen have the wrong timezone offset file, that's all. Next week it
doesn't matter. I may leave them turned off for another week

Grant.
--
Memory fault -- brain fried