my slack box doesn't shift automatically to summer time, is that
normal?
heavytull

heavytull wrote:
> my slack box doesn't shift automatically to summer time, is that
> normal?
> heavytull
>
>
Depends -- where are you, have you installed the patches for your
Slackware version?

Try

wget ftp://ftp.osuosl.org/pub/slackware/s...11.0/patches/*

(which will get all the patches for Slackware 11.0 -- change the '-11.0'
to whatever your release is) then use

upgradepkg *.tgz

to apply them all.

--
Jus' livin' in the Dilbert Zone...

On Sun, 25 Mar 2007 09:05:09 -0700, heavytull wrote:

> my slack box doesn't shift automatically to summer time, is that
> normal?
> heavytull

For lack of an update to handle the new DST times, yes, that would be
normal.

ray wrote:
> On Sun, 25 Mar 2007 09:05:09 -0700, heavytull wrote:
>
>> my slack box doesn't shift automatically to summer time, is that
>> normal?
>> heavytull
>
> For lack of an update to handle the new DST times, yes, that would be
> normal.
>
This has nothing to do with the updates to handle the recent change in
American DST times.

According to his "NNTP-Posting-Host: 86.68.148.142" is "heavytull"
posting from France. Europe switched last night (Sun, Mar 25, 2:00 AM)
to DST.

Your computer was probably switched off at Mar 25, 2:00 AM _and_ your
hardware clock (BIOS clock, whatever name you want to use) is running
local time I suppose.

When your system is configured for a hardware clock running at local
time, Linux is supposing your clock shows the _actual_ local time
during a boot. The clock will not be incremented or decremented if
the DST changed during the period that the computer was switched off.

If you are used to MS Windows you might expect Linux to change
the hardware clock during the first boot after a DST change, but that
also will create time errors in certain circumstances.
Take a multi-boot Windows system as an example with two or more
different windows versions. _Each_ windows version will change the clock
during the first boot of _that_ version after a DST change. And that
is certainly not what you want.

If you have a multi-boot system with windows installed it is probably
most convenient to run your hardware clock at local time. In that case
you should be aware that windows will change your clock at first boot
after as DST change and that Linux won't do that. If you are running
a Linux-only system you really should configure that system to run
the hardware clock at UTC. UTC has no DST so there is no need to adjust
a clock running at UTC after a DST change.


Regards,

Kees.

--
Kees Theunissen

On Sun, 25 Mar 2007 09:05:09 -0700, heavytull wrote:

> my slack box doesn't shift automatically to summer time, is that
> normal?
> heavytull
>
It should automatically adjust the time. I checked this on my system as
follows:

1. Ran timeconfig and set the timezone to "Europe/Paris"

# zdump -v /etc/localtime| grep 2007
/etc/localtime Sun Mar 25 00:59:59 2007 UTC = Sun Mar 25 01:59:59 2007 CET isdst=0 gmtoff=3600
/etc/localtime Sun Mar 25 01:00:00 2007 UTC = Sun Mar 25 03:00:00 2007 CEST isdst=1 gmtoff=7200
/etc/localtime Sun Oct 28 00:59:59 2007 UTC = Sun Oct 28 02:59:59 2007 CEST isdst=1 gmtoff=7200
/etc/localtime Sun Oct 28 01:00:00 2007 UTC = Sun Oct 28 02:00:00 2007 CET isdst=0 gmtoff=3600

2. Switched back to my actual timezone. "April in Paris" doesn't seem
very likely for me. ;-)

BTW, there were some posts about the US' DST change which went into
effect earlier this year. Is there a similar change in France? Other than
that, I don't know what to say, other than you should make sure you have
the latest Slackware patches applied.

--
Douglas Mayne

On 2007-03-25, heavytull wrote:
> my slack box doesn't shift automatically to summer time, is that
> normal?

Sure. It's not summer time yet.

Duh.


--
"Ubuntu" - an African word meaning "Slackware is too hard for me".

Kees Theunissen wrote:

> ray wrote:
>> On Sun, 25 Mar 2007 09:05:09 -0700, heavytull wrote:
>>
>>> my slack box doesn't shift automatically to summer time, is that
>>> normal?
>>> heavytull
>>
>> For lack of an update to handle the new DST times, yes, that would be
>> normal.
>>
> This has nothing to do with the updates to handle the recent change in
> American DST times.
>
> According to his "NNTP-Posting-Host: 86.68.148.142" is "heavytull"
> posting from France.
I never find such info about users in iether google groups or knode; how do you
do?

anyway...

> Europe switched last night (Sun, Mar 25, 2:00 AM)
> to DST.

yes

>
> Your computer was probably switched off at Mar 25, 2:00 AM
I actually do not remember

> _and_ your
> hardware clock (BIOS clock, whatever name you want to use) is running
> local time I suppose.
what you call local time? the time of the country i'm living in?
then yes.
>
> When your system is configured for a hardware clock running at local
> time
how does it guess?
there is an option in the bios to run whether at local time or UTC?


> , Linux is supposing your clock shows the _actual_ local time
> during a boot. The clock will not be incremented or decremented if
> the DST changed during the period that the computer was switched off.
>

> If you are used to MS Windows you might expect Linux to change
> the hardware clock during the first boot after a DST change, but that
> also will create time errors in certain circumstances.
> Take a multi-boot Windows system as an example with two or more
> different windows versions. _Each_ windows version will change the clock
> during the first boot of _that_ version after a DST change. And that
> is certainly not what you want.
>
yes, i have never though about that circumstance!

> If you have a multi-boot system with windows
that is my case

> installed it is probably
> most convenient to run your hardware clock at local time. In that case
> you should be aware that windows will change your clock at first boot
> after as DST change and that Linux won't do that. If you are running
> a Linux-only system you really should configure that system to run
> the hardware clock at UTC. UTC has no DST so there is no need to adjust
> a clock running at UTC after a DST change.
>
if i configure my hardware clock to run at UTC, will windows change it anyway?
or will it just add the necessary delay softly (i mean without changing
anything in the hardware (which i don't like))

If my hardware clock is running at UTC, would linux have changed its time for
DST at first boot after the official switch?



>
> Regards,
>
> Kees.
>

--
heavytull

On Sat, 31 Mar 2007 16:20:22 +0200, heavytull wrote:

> Kees Theunissen wrote:
>
>> ray wrote:
>>> On Sun, 25 Mar 2007 09:05:09 -0700, heavytull wrote:
>>>
....
>> This has nothing to do with the updates to handle the recent change in
>> American DST times.
>>
>> According to his "NNTP-Posting-Host: 86.68.148.142" is "heavytull"
>> posting from France.
> I never find such info about users in iether google groups or knode;

In knode I don't remember as it's quite a long time since I
last tried it to check if it was getting up to something I
could use.
In GooGroop you'll have to turn on the "Original/Full/Source" whatever
is the new term in their last betatest dreamed by some 5 years
cousin in law that'd just had an idea about how to make GooGroops
be a PITA a little bit more than 5 minutes ago, over, and over again...


> how
> do you do?

Fine, thanks )

Just ask this question to Serge Ribeiro and/or Audrey Maruani ;-)

Anyway, I can see you just switched from FT-Nordnet-GaoLand to
some privy `"tor"red' nntp GW so, you're now possibly not the "real"
"heavytull" but, since you can fetch an IP@ you always can try
to check if that's a lead in a twine or wôt:

dig -x IP@

may give a step, and if it gives just use it whith 'whois'

Cheers

loki harfagr wrote :

> In knode I don't remember as it's quite a long time since I
> last tried it to check if it was getting up to something I
> could use.

In KNode its "View"->"Headers"->"All Headers".
--
Thomas O.

This area is designed to become quite warm during normal operation.

On Sat, 31 Mar 2007 16:20:22 +0200, heavytull wrote:

> Kees Theunissen wrote:
>
>> When your system is configured for a hardware clock running at local
>> time
> how does it guess?
> there is an option in the bios to run whether at local time or UTC?

Not in the BIOS. When you installed Slackware, it asked you if your clock
was set to local time or UTC. According to /usr/doc/Linux-HOWTOs/Clock,
this is stored in /etc/adjtime. Unless you synchronize it with an NTP
server, or deliberately change the hardware clock yourself, Linux doesn't
change the hardware clock of your PC, it just changes what it displays to
users as the current time.

> if i configure my hardware clock to run at UTC, will windows change it
> anyway? or will it just add the necessary delay softly (i mean without
> changing anything in the hardware (which i don't like))

Yes, Windows will change the time for seasonal DST, but it will display
UTC as the local time. (Please note that the latest version of Windows I
have any experience with during a DST change is Win98SE.)

> If my hardware clock is running at UTC, would linux have changed its
> time for DST at first boot after the official switch?

[Two comments in-line.]
No, but it would make the adjustment to what it displays as your local
time. For a PC with Windows and Linux on it, the best advice is to use
Windows to set your hardware clock to local time, and then boot Windows to
change the clock for DST-type time changes. However, if you don't care if
Windows knows the correct local time, set the clock to UTC and disable
Windows' ability to change the clock for DST. Just make sure /etc/adjtime
reflects your wishes so that Linux time is correct.

--
Chick Tower

For e-mail: aols . sent . towerboy AT xoxy . net