Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.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 03:02:07 -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 00:02:02 -0800 Message-ID: <87ppdh28w5.fld@barrow.com> User-Agent: gnus 5.10.6/XEmacs 21.4.15/Linux 2.6.19 Cancel-Lock: sha1:2eXzzmClENt0kGThbblWr7N9wJo= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 84 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 24.237.125.254 X-Trace: sv3-zujXG4ajql588cq+H9wrY334nwh+4t4HNkRmlYcRQR13ESUXq+13pH8HdN275pueIaOJlVFiYutgahp!jN13w43Vllo8WdZuKL1TDjICR/FPpR6RSFxSl7XnYQWM+PpVmwyXc5ViYW8q0zvTlRpAj+o5 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: 4931 Xref: csiph.com comp.os.linux.misc:12441 "Nuno J. Silva (aka njsg)" wrote: >["Followup-To:" header set to comp.os.linux.misc.] >On 2014-10-24, Floyd L. Davidson wrote: >> "Chester A. Arthur" wrote: >>>On Thu, 23 Oct 2014 06:07:23 +0000, not.socialnetwork wrote: >>> >>>> PS. how do you easily set the RTC back by 7 minutes, >>>> without decoding the absurd `man'? >>> >>>Set the system clock correctly with the date command, then >>>run 'sudo hwclock -w', assuming TZ is set properly. >> >> /usr/sbin/ntpdate -b us.pool.ntp.org >> >>>Read the rtc with 'cat /proc/driver/rtc|head -1' or something >>>similar on most linuxes. >> >> Why not just invoke the "date" command. > >Actually, at least on linux, date (software clock) and the RTC are >different things. In this case, Chester's answer was actually much >better than mine from yesterday: in this case, we're actually reading >the time from the RTC, and the question was "how do you [...] set the >RTC back by [...]". The procedure recommended above syncronizes them first. /usr/sbin/ntpdate -b us.pool.ntp.org # set the system clock hwclock -w # set the hardware clock date # get the date >>>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. > >I actually don't know what's the default for Gentoo. This at least used >to be documented in the handbook. But I've got so used to the install >procedure that I just look it up and make sure that it's set to UTC. > >> >> Most people will be *far* better served setting the >> hwclock to local time than to UTC. > >Actually, if you live in a place where DST exists, for example, all of >the mainland european union, and at least some of the other EU >territories, and set the hwclock to local time, you open a pandora's box >of problems: How do you know in which timezone the RTC is the next time >you boot up after DST? I've never lived anywhere that does not have DST, and never had a problem with that. I have a cron job that runs "ntbdate -b" regularly. I have another that runs "hwclock -w" regularly too. >If you're dual booting with windows, although Microsoft has not >officially endorsed the option, you can set Windows to treat the RTC as >being UTC, thus getting rid of yet another problem (which operating >system changes the RTC to make up for DST, and when?). > >The option is not officially endorsed because it has not been hard >tested and sometimes may have issues, but these are documented in >Microsoft's Knowledge Base. Microsoft Windows NT 6.1 (Windows 7 and >Server 2008 R2) and possibly older versions support this option. > >Unless you have a strong reason not to keep the RTC in UTC, my humble >opinion is that you should leave it as UTC to avoid breakage: this way, >there's no ambiguity as to what the RTC time stands for. There is no ambiguity. >>>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. -- Floyd L. Davidson http://www.apaflo.com/ Ukpeagvik (Barrow, Alaska) floyd@apaflo.com