Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #12430 > unrolled thread

what VESA/vga *AM* I useing?

Started bynot.socialnetwork@gmail.com
First post2014-10-23 06:07 +0000
Last post2014-10-25 19:54 +0200
Articles 6 on this page of 46 — 14 participants

Back to article view | Back to comp.os.linux.misc

Contents

  what VESA/vga *AM* I useing? not.socialnetwork@gmail.com - 2014-10-23 06:07 +0000
    Re: what VESA/vga *AM* I useing? "Nuno J. Silva (aka njsg)" <njsg@invalid.invalid> - 2014-10-23 08:22 +0000
    Re: what VESA/vga *AM* I useing? not.socialnetwork@gmail.com - 2014-10-23 12:04 +0000
      Re: what VESA/vga *AM* I useing? Joe Beanfish <joebeanfish@nospam.duh> - 2014-10-23 13:25 +0000
        Re: what VESA/vga *AM* I useing? not.socialnetwork@gmail.com - 2014-10-24 06:14 +0000
    Re: what VESA/vga *AM* I useing? ebenZEROONE@verizon.net (Hactar) - 2014-10-23 21:45 -0400
      Re: what VESA/vga *AM* I useing? "Nuno J. Silva (aka njsg)" <njsg@invalid.invalid> - 2014-10-24 06:56 +0000
      Re: what VESA/vga *AM* I useing? Unknown <dog@gmail.com> - 2014-10-26 03:07 +0000
    Re: what VESA/vga *AM* I useing? "Chester A. Arthur" <deadprez@whitehouse.com> - 2014-10-23 22:18 -0500
      Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-23 22:09 -0800
        Re: what VESA/vga *AM* I useing? "Nuno J. Silva (aka njsg)" <njsg@invalid.invalid> - 2014-10-24 07:07 +0000
          Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-24 00:02 -0800
        Re: what VESA/vga *AM* I useing? Rich <rich@example.invalid> - 2014-10-24 12:46 +0000
          Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-24 05:39 -0800
            Re: what VESA/vga *AM* I useing? John Hasler <jhasler@newsguy.com> - 2014-10-24 09:31 -0500
              Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-24 08:37 -0800
                Re: what VESA/vga *AM* I useing? John Hasler <jhasler@newsguy.com> - 2014-10-24 12:09 -0500
                  Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-24 09:30 -0800
                    Re: what VESA/vga *AM* I useing? John Hasler <jhasler@newsguy.com> - 2014-10-24 12:44 -0500
                      Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-24 10:15 -0800
                        Re: what VESA/vga *AM* I useing? Rich <rich@example.invalid> - 2014-10-24 18:38 +0000
                          Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-24 11:09 -0800
                            Re: what VESA/vga *AM* I useing? Richard Kettlewell <rjk@greenend.org.uk> - 2014-10-24 21:31 +0100
                              Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-24 12:53 -0800
                                Re: what VESA/vga *AM* I useing? Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2014-10-25 13:56 +0100
                                  Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-25 05:12 -0800
                                    Re: what VESA/vga *AM* I useing? John Hasler <jhasler@newsguy.com> - 2014-10-25 09:24 -0500
                                      Re: what VESA/vga *AM* I useing? Rich <rich@example.invalid> - 2014-10-26 00:15 +0000
                        Re: what VESA/vga *AM* I useing? John Hasler <jhasler@newsguy.com> - 2014-10-24 14:17 -0500
                          Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-24 12:55 -0800
                            Re: what VESA/vga *AM* I useing? John Hasler <jhasler@newsguy.com> - 2014-10-24 16:23 -0500
                            Re: what VESA/vga *AM* I useing? Richard Kettlewell <rjk@greenend.org.uk> - 2014-10-24 22:33 +0100
                    Re: what VESA/vga *AM* I useing? Rich <rich@example.invalid> - 2014-10-24 18:28 +0000
                      Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-24 10:43 -0800
                        Re: what VESA/vga *AM* I useing? Rich <rich@example.invalid> - 2014-10-24 22:52 +0000
                      Re: what VESA/vga *AM* I useing? Eef Hartman <E.J.M.Hartman@gmail.com> - 2014-10-24 18:57 +0000
            Re: what VESA/vga *AM* I useing? Rich <rich@example.invalid> - 2014-10-24 17:04 +0000
            Re: what VESA/vga *AM* I useing? Eef Hartman <E.J.M.Hartman@gmail.com> - 2014-10-24 17:09 +0000
              Re: what VESA/vga *AM* I useing? Allodoxaphobia <knock_yourself_out@example.net> - 2014-10-24 21:02 +0000
                Re: what VESA/vga *AM* I useing? John Hasler <jhasler@newsguy.com> - 2014-10-24 16:30 -0500
                  Re: what VESA/vga *AM* I useing? Martin <m@abc.invalid> - 2014-10-25 14:40 +0200
                    Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-25 04:50 -0800
                      Re: what VESA/vga *AM* I useing? John Hasler <jhasler@newsguy.com> - 2014-10-25 09:17 -0500
                        Re: what VESA/vga *AM* I useing? floyd@apaflo.com (Floyd L. Davidson) - 2014-10-25 13:26 -0800
                          Re: what VESA/vga *AM* I useing? John Hasler <jhasler@newsguy.com> - 2014-10-25 16:49 -0500
                      Re: what VESA/vga *AM* I useing? Martin <m@abc.invalid> - 2014-10-25 19:54 +0200

Page 3 of 3 — ← Prev page 1 2 [3]

#12466

FromMartin <m@abc.invalid>
Date2014-10-25 14:40 +0200
Message-ID<m2g5ng$49p$1@online.de>
In reply to#12464
On 10/24/2014 11:30 PM, John Hasler wrote:
> Allodoxaphobia writes:
>> *NOT* my experience here.  And this system is *ALWAYS* off overnight
>>   when The Change occurs -- going back 15 years.
>
> How is your BIOS clock getting set forward or back an hour in order to
> continue to reflect local time after the Change occurs?
>

That is usally done by the operating system next time you boot, which 
also means if you have more than one OS installed you get the 1 hour 
correction applied every time you boot into an OS for the first time 
after the change-over.

ntp alleviates the situation a bit, but it is a clumsy workaround for an 
issue that can be avoided by doing the intelligent thing - running your 
hardware clock in UTC.

[toc] | [prev] | [next] | [standalone]

#12467

Fromfloyd@apaflo.com (Floyd L. Davidson)
Date2014-10-25 04:50 -0800
Message-ID<87mw8kz52s.fld@barrow.com>
In reply to#12466
Martin <m@abc.invalid> wrote:
>On 10/24/2014 11:30 PM, John Hasler wrote:
>> Allodoxaphobia writes:
>>> *NOT* my experience here.  And this system is *ALWAYS* off overnight
>>>   when The Change occurs -- going back 15 years.
>>
>> How is your BIOS clock getting set forward or back an hour in order to
>> continue to reflect local time after the Change occurs?
>>
>
>That is usally done by the operating system next time
>you boot, which also means if you have more than one OS
>installed you get the 1 hour correction applied every
>time you boot into an OS for the first time after the
>change-over.
>
>ntp alleviates the situation a bit, but it is a clumsy
>workaround for an issue that can be avoided by doing the
>intelligent thing - running your hardware clock in UTC.

But ntp is not a clumsy workaround for anything.  It is
an elegant way to assure an accurate clock.  If it does
that to 1/100 of a second every day, or to the  hour on
two days of the year, is immaterial.  It does it.

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

[toc] | [prev] | [next] | [standalone]

#12470

FromJohn Hasler <jhasler@newsguy.com>
Date2014-10-25 09:17 -0500
Message-ID<87ppdgjksv.fsf@thumper.dhh.gt.org>
In reply to#12467
Floyd L. Davidson writes:
> But ntp is not a clumsy workaround for anything.  It is an elegant way
> to assure an accurate clock.

An accurate UTC clock.  NTP knows nothing about local time.
-- 
John Hasler 
jhasler@newsguy.com
Dancing Horse Hill
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]

#12473

Fromfloyd@apaflo.com (Floyd L. Davidson)
Date2014-10-25 13:26 -0800
Message-ID<878uk3zvrk.fld@barrow.com>
In reply to#12470
John Hasler <jhasler@newsguy.com> wrote:
>Floyd L. Davidson writes:
>> But ntp is not a clumsy workaround for anything.  It is an elegant way
>> to assure an accurate clock.
>
>An accurate UTC clock.  NTP knows nothing about local time.

I doesn't need to, and your hardware clock need not be UTC.

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

[toc] | [prev] | [next] | [standalone]

#12474

FromJohn Hasler <jhasler@newsguy.com>
Date2014-10-25 16:49 -0500
Message-ID<8761f7kef4.fsf@thumper.dhh.gt.org>
In reply to#12473
Floyd L. Davidson writes:
> ...your hardware clock need not be UTC.

Right, because it serves only to keep time while the machine is off.  So
what is the point in setting it to local time and forcing the OS to
apply arcane local rules to figure out what UTC is so that it can set
the system clock on startup?  Much simpler just to write out UTC at
shutdown and read it back at startup.
-- 
John Hasler 
jhasler@newsguy.com
Dancing Horse Hill
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]

#12472

FromMartin <m@abc.invalid>
Date2014-10-25 19:54 +0200
Message-ID<m2go4d$ji9$1@online.de>
In reply to#12467
On 10/25/2014 02:50 PM, Floyd L. Davidson wrote:
> But ntp is not a clumsy workaround for anything.

I didn't say ntp is clumsy IN ITSELF.

However, using ntp to correct the fact that multiple operating systems 
on your machine mess up your hardware clock because each one feels the 
need to correct your local time not knowing about the others, IS clumsy.

And the clumsy workaround fails, when there is no network access.

Use UTC instead.

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | comp.os.linux.misc

csiph-web