Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!border1.nntp.dca1.giganews.com!Xl.tags.giganews.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!local2.nntp.dca.giganews.com!nntp.posted.gcicommunications!news.posted.gcicommunications.POSTED!not-for-mail
NNTP-Posting-Date: Fri, 24 Oct 2014 15:53:55 -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> <87y4s5edzg.fsf@thumper.dhh.gt.org> <87h9yt1l0x.fld@barrow.com> <87ppdhe6od.fsf@thumper.dhh.gt.org> <87d29h1ik7.fld@barrow.com> <87lho5e51q.fsf@thumper.dhh.gt.org> <878uk51ghf.fld@barrow.com> <m2e6br$f7m$1@dont-email.me> <87zjclz3ln.fld@barrow.com> <wwv8uk52or0.fsf@l1AntVDjLrnP7Td3DQJ8ynzIq3lJMueXf87AxnpFoA.invalid>
From: floyd@apaflo.com (Floyd L. Davidson)
Organization: __________
Date: Fri, 24 Oct 2014 12:53:52 -0800
Message-ID: <87vbn9yysf.fld@barrow.com>
User-Agent: gnus 5.10.6/XEmacs 21.4.15/Linux 2.6.19
Cancel-Lock: sha1:VN2FIUEotnc3/PgWuPwJFDQ5Ng4=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 23
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 24.237.125.254
X-Trace: sv3-kz0DM+51tBbqT9YVkndnawxbKuJsQYUTetq4YyjTR5Brf3fRxDXJhh49tXypxR6mtqdPEvUpBcT8nGS!d2RADB5uQrgl89jUkE0jR3+TmIcEUgj+TupjONTpKMpCgGrXcnbFHnrayCZbWq+u7nczrgtN
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: 2590
Xref: csiph.com comp.os.linux.misc:12459

Richard Kettlewell <rjk@greenend.org.uk> wrote:
>floyd@apaflo.com (Floyd L. Davidson) writes:
>> Rich <rich@example.invalid> wrote:
>>> That's what is meant by "everything just works".  The clocks do not
>>> get reprogrammed at all, but the visible time to you is the correct
>>> time you expect, even with no sync. to any external network time
>>> source.
>>
>> Wrong.  The hardware clock is not changed, but the system clock is.
>
>The system clock is maintained by the kernel, which no idea what
>timezone it is or what DST rules are in force; that is domain of the
>timezone support code in the C library.  As such if you call time() one
>second before a DST change and again one second after the change, the
>result will differ by 2.

Okay, it isn't the system clock that is changed, it's
the user land interface.  The point is that the output
of the date command will change.

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