On Thu, Jun 20, 2013 at 01:36:02PM +0400, Konstantin Khomoutov wrote:
> > Why is UTC time bogus?
>
> Well, I am simply afraid of a possible knee-jerk reaction of an admin
> who for whatever reason manages to hit the BIOS setup program and sees
> martian time there, which they would likely attempt
On Thu, 20 Jun 2013 10:47:12 +0300
Andrei POPESCU wrote:
> > > Storing local time in the hardware clock is utterly wrong for many
> > > reasons. The only reason Microsoft have continued to ship Windows
> > > configured this way is the usual backwards-compatibility problem.
> > > If you're running
Am 19.06.2013 18:12, schrieb Steve Langasek:
> The *only* argument for using local time in the system clock is so that the
> time displayed in the timezone-ignorant BIOS will be correct. But who looks
> at the time in the BIOS anyway?
Windows is doing ;)
signature.asc
Description: OpenPGP dig
Steve McIntyre einval.com> writes:
> So apply the registry fix if you care about a system with the
This is probably bad advice:
http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html
tl;dr: Running NT with RTC in UTC and timezone ≠ UTC is buggy.
Of course, just setting a UTC timezone (without any D
On Jo, 20 iun 13, 08:50:33, Lars Wirzenius wrote:
> On Thu, Jun 20, 2013 at 10:47:12AM +0300, Andrei POPESCU wrote:
> > Why is UTC time bogus?
>
> If you set your BIOS clock to show the current time in the UTC time zone,
> it will confuse people who think the BIOS clock shows the local time on
> M
On Thu, Jun 20, 2013 at 10:47:12AM +0300, Andrei POPESCU wrote:
> Why is UTC time bogus?
If you set your BIOS clock to show the current time in the UTC time zone,
it will confuse people who think the BIOS clock shows the local time on
Mars.
--
http://www.cafepress.com/trunktees -- geeky funny T-
On Mi, 19 iun 13, 17:27:56, Konstantin Khomoutov wrote:
> On Wed, 19 Jun 2013 13:39:31 +0100
> Steve McIntyre wrote:
>
> [...]
>
> > Storing local time in the hardware clock is utterly wrong for many
> > reasons. The only reason Microsoft have continued to ship Windows
> > configured this way is
On Wed, Jun 19, 2013 at 09:39:11PM +0200, Bas Wijnen wrote:
> On Wed, Jun 19, 2013 at 07:56:26PM +0100, Ben Hutchings wrote:
> > On Wed, Jun 19, 2013 at 09:12:37AM -0700, Steve Langasek wrote:
> > [...]
> > > The *only* argument for using local time in the system clock is so that
> > > the
> > > t
On Wed, Jun 19, 2013 at 07:56:26PM +0100, Ben Hutchings wrote:
> On Wed, Jun 19, 2013 at 09:12:37AM -0700, Steve Langasek wrote:
> [...]
> > The *only* argument for using local time in the system clock is so that the
> > time displayed in the timezone-ignorant BIOS will be correct. But who looks
>
On Wed, Jun 19, 2013 at 09:12:37AM -0700, Steve Langasek wrote:
[...]
> The *only* argument for using local time in the system clock is so that the
> time displayed in the timezone-ignorant BIOS will be correct. But who looks
> at the time in the BIOS anyway?
No, the major reason is compatibility
On Wed, Jun 19, 2013 at 09:10:06AM +0100, Darac Marjal wrote:
> This isn't actually an error. But perhaps an issue with PC design. The
> internal clock of your PC stores a time and date, but it DOESN'T store
> which time zone you're in. All it stores is, for example, "20:20".
> When you install a
On Wed, 19 Jun 2013 13:39:31 +0100
Steve McIntyre wrote:
[...]
> Storing local time in the hardware clock is utterly wrong for many
> reasons. The only reason Microsoft have continued to ship Windows
> configured this way is the usual backwards-compatibility problem. If
> you're running on a sys
On Wed, Jun 19, 2013 at 05:27:56PM +0400, Konstantin Khomoutov wrote:
>On Wed, 19 Jun 2013 13:39:31 +0100
>Steve McIntyre wrote:
>
>[...]
>
>> Storing local time in the hardware clock is utterly wrong for many
>> reasons. The only reason Microsoft have continued to ship Windows
>> configured this
Darac Marjal wrote:
>
>This isn't actually an error. But perhaps an issue with PC design. The
>internal clock of your PC stores a time and date, but it DOESN'T store
>which time zone you're in. All it stores is, for example, "20:20".
>
>When you install a new OS, it reads that time and must make on
On Wed, Jun 19, 2013 at 01:43:08AM +0400, Maxim Markov wrote:
>Hello.
>
>I use debian-live-7.0.0-amd64-gnome-desktop.
>And it has error in Time Zones Settings.
>System Time changes during installation.
>It`s possible that date can changes too.
>
>for example:
>when i
15 matches
Mail list logo