Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!peer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!Xl.tags.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.posted.gcicommunications!news.posted.gcicommunications.POSTED!not-for-mail
NNTP-Posting-Date: Sat, 25 Oct 2014 07:50:21 -0500
Newsgroups: comp.os.linux.misc,alt.os.linux.slackware,alt.os.linux.debian
Subject: Re: what VESA/vga *AM* I useing?
References: <m2a5ur$e5b$1@dont-email.me> <KvOdnR_HGMKLWNTJnZ2dnUU7-UWdnZ2d@posted.cavenetllc> <87tx2u0zit.fld@barrow.com> <m2dhmn$rhv$2@dont-email.me> <87lho51tag.fld@barrow.com> <544a87b1$0$2927$e4fe514c@news2.news.xs4all.nl> <slrnm4lfkf.aps.knock_yourself_out@vps.jonz.net> <878uk5dukx.fsf@thumper.dhh.gt.org> <m2g5ng$49p$1@online.de>
From: floyd@apaflo.com (Floyd L. Davidson)
Organization: __________
Date: Sat, 25 Oct 2014 04:50:19 -0800
Message-ID: <87mw8kz52s.fld@barrow.com>
User-Agent: gnus 5.10.6/XEmacs 21.4.15/Linux 2.6.19
Cancel-Lock: sha1:2Pa3rhXJ+Mw+zKe2VfN2wT7eCqc=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 28
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 24.237.125.254
X-Trace: sv3-hQSRRIfAMLK1atIvrYBKnQOPu77r+PXpulC9QFdowJ5vQy9bosS0jzdt/LuQ6XdIkwfylbIAPtERwqP!ZqtDLXhaov+MC0AYQEPy5ThAvUMFEJdHPg01IqUaq12xbwJCipSAkZlH7dmFiwpUBlwVaLtn
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2544
X-Received-Bytes: 2656
X-Received-Body-CRC: 807929587
Xref: csiph.com comp.os.linux.misc:12467

Martin <m@abc.invalid> wrote:
>On 10/24/2014 11:30 PM, John Hasler wrote:
>> Allodoxaphobia writes:
>>> *NOT* my experience here.  And this system is *ALWAYS* off overnight
>>>   when The Change occurs -- going back 15 years.
>>
>> How is your BIOS clock getting set forward or back an hour in order to
>> continue to reflect local time after the Change occurs?
>>
>
>That is usally done by the operating system next time
>you boot, which also means if you have more than one OS
>installed you get the 1 hour correction applied every
>time you boot into an OS for the first time after the
>change-over.
>
>ntp alleviates the situation a bit, but it is a clumsy
>workaround for an issue that can be avoided by doing the
>intelligent thing - running your hardware clock in UTC.

But ntp is not a clumsy workaround for anything.  It is
an elegant way to assure an accurate clock.  If it does
that to 1/100 of a second every day, or to the  hour on
two days of the year, is immaterial.  It does it.

-- 
Floyd L. Davidson                         http://www.apaflo.com/
Ukpeagvik (Barrow, Alaska)                      floyd@apaflo.com