Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.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: Fri, 24 Oct 2014 13:43:56 -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> From: floyd@apaflo.com (Floyd L. Davidson) Organization: __________ Date: Fri, 24 Oct 2014 10:43:50 -0800 Message-ID: <874mut1f6h.fld@barrow.com> User-Agent: gnus 5.10.6/XEmacs 21.4.15/Linux 2.6.19 Cancel-Lock: sha1:nzl8ZJgiLg6Zxzuv9VBB0zoddXg= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 65 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 24.237.125.254 X-Trace: sv3-Wu6HtvN1/K8HkmvTLXQqetaNa90i5ZBmlz1azShpEDN5bfp7qzsabA1eRTMf4N6nG8yMINLisUpxziZ!W5usamryZT+mvUvkGiAydlh2fFG6MLaMVqeCgTKTuZuVphbkI8MVKX7zectZkXQ4ClmOY0SM 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: 3884 Xref: csiph.com comp.os.linux.misc:12454 Rich wrote: >In comp.os.linux.misc Floyd L. Davidson wrote: >> John Hasler wrote: >> >Floyd L. Davidson writes: >> >> The only way I know when the switch takes place is when I notice my >> >> computer is an hour different than my wall clock. >> > >> >I wrote: >> >> Same here with the BIOS clock set to UTC. So what is the advantage of >> >> setting it to local time and having to change it manually twice a year? >> > >> >Floyd L. Davidson writes: >> >> So why would anyone manually change it? >> > >> >If you don't it will only be on local time part of the year. > >> I've had multiple systems set to local time since the >> early 90's. They all switch automatically. > >> A cron job sets the time with ntpdate. > >Ah, this might be why then. Ntpdate might also be applying DST >translations for you, and you see the clock shift. > >My statements were based upon setting HW clock and system time in UTC, >and then the shift occurs automatically, even with no network >connection to anything running. Your statement was "and having to change it manually". That just isn' the case. >> Another cron job sets the hardware clock from the system clock. Both >> run once an hour. > >> It's all automatic. > >Yes, and ntpdate is likely why you are seeing auto DST shift changes. >Without it, you would not see the time shift on the computer either. But I do see it all work automatically. That's what a good systems admin sets the system up to do... ;-) >> The big problem is my wall clock... I have to manually set it. > >They do make wall clocks now that sync to transmitted time signals and >auto-set themselves. Although depending upon where you are located >geographically will determine if such would even work for you. The don't work at 71 degrees north latitude. Oh, I forgot, there is another problem... my danged cameras don't auto switch either. Nor do my printers. For the life of me I cannot understand why Nikon and Epson both have not put an embedded Linux system into every product they make! Damned foolish, considering the vast benefits. Epson in particular has a crude human interface that reminds of what was being done in the 80's with 8085 and Z80 microprocessors. It's ridiculous, and so easy to fix. -- Floyd L. Davidson http://www.apaflo.com/ Ukpeagvik (Barrow, Alaska) floyd@apaflo.com