Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!border2.nntp.dca1.giganews.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 08:12:24 -0500 Newsgroups: comp.os.linux.misc,alt.os.linux.slackware,alt.os.linux.debian Subject: Re: what VESA/vga *AM* I useing? References: <87tx2u0zit.fld@barrow.com> <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> <87zjclz3ln.fld@barrow.com> <87vbn9yysf.fld@barrow.com> <20141025135621.684dd4d0@bother.homenet> From: floyd@apaflo.com (Floyd L. Davidson) Organization: __________ Date: Sat, 25 Oct 2014 05:12:23 -0800 Message-ID: <87ioj8z420.fld@barrow.com> User-Agent: gnus 5.10.6/XEmacs 21.4.15/Linux 2.6.19 Cancel-Lock: sha1:G/U1l6yrESWwSlotCidFKBpxLMg= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 33 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 24.237.125.254 X-Trace: sv3-rzMvCYV53k+Z+wzgRqslcsLWp2F08s1dlKgOR6glWaMij5x5MTMyJXq3XouWPGIpprB2zy8/0AjyHGT!SMQ+Grai2sNVrNxmuewGy4BiRDbU+m8eFz4tG9wOEqRFkYV6kl11g+lUXLh87a2dHGWrXt3H 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: 3170 Xref: csiph.com comp.os.linux.misc:12469 Chris Vine wrote: >On Fri, 24 Oct 2014 12:53:52 -0800 >floyd@apaflo.com (Floyd L. Davidson) wrote: >> Richard Kettlewell wrote: >> >floyd@apaflo.com (Floyd L. Davidson) writes: >> >> Rich 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. > >And to go back to the original point, this means that setting your hw >clock to UTC is much more convenient than setting it to localtime. >As you say, there is no switching, just the output of date changes - >which is how it should be. Why is that "how it should be"? It doesn't make life better... -- Floyd L. Davidson http://www.apaflo.com/ Ukpeagvik (Barrow, Alaska) floyd@apaflo.com