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: Fri, 24 Oct 2014 08:39:05 -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> From: floyd@apaflo.com (Floyd L. Davidson) Organization: __________ Date: Fri, 24 Oct 2014 05:39:03 -0800 Message-ID: <87lho51tag.fld@barrow.com> User-Agent: gnus 5.10.6/XEmacs 21.4.15/Linux 2.6.19 Cancel-Lock: sha1:m4PsU8Bxo17OJOLi/oz9rMYe1pU= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 46 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 24.237.125.254 X-Trace: sv3-ax8m5P123woxEkJ6UKiXYjQF9AA0eyToj9F3z9rShjM9WijOxrHapgqYDidHct+g+9nrexSm/kmnM31!tr+HxdYCW0U0xe/ypkzobFnb+1HlQULc24vmwgqXxxpNU1m+XmDi7dwk+WfR5ND8o+XU2YC2 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: 3254 Xref: csiph.com comp.os.linux.misc:12443 Rich wrote: >In comp.os.linux.misc Floyd L. Davidson wrote: >> "Chester A. Arthur" wrote: >> >One should always keep the hwclock in UTC. System time will change >> >with the rules for your local time zone, and computers move, >> >especially laptops. Most linuxes these days follow these rules, >> >except the gentoo family. Slackware gives you an explicit choice at >> >install--choose UTC. The BSDs I have tried give no choice, they set >> >the hwclock to localtime, that's dumb. > >> Most people will be *far* better served setting the hwclock to local >> time than to UTC. > >How so? Unless they need to dual-boot windows, setting the hardware >clock to UTC will allow their computer to automatically shift back and >forth due to the idiot politicians desire to play with the clocks >(i.e., daylight savings time). All of mine have been shifting between AKDT and AKST spring and fall every year for a very long time... >> >Localtime is crazy, the rules change and there are so many >> >strangenesses. (The world ends at midnite-12:30 Newfie time). There >> >is software to deal with that, and it works well if it isn't >> >bypassed by OSes that make poor choices. > >> You're making life much more difficult than it need be. > >And setting the hardware clock to UTC lets the system libs take care >of that crazyness, so that one's computer time automatically moves >forward at 2am in the spring, and automatically falls back at 2am in >the fall, with no effort on the users part. Setting to local time does not change that. >That seems the very definition of "much easier" rather than more >difficult. Let the computer do the work, both of remembering when, and >of how much to shift. The only way I know when the switch takes place is when I notice my computer is an hour different than my wall clock. -- Floyd L. Davidson http://www.apaflo.com/ Ukpeagvik (Barrow, Alaska) floyd@apaflo.com