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 one of two >assumtions: Either the time is stored as local time (in which case no >adjustment is necessary, but there may be issues when Daylight Saving >Time comes into effect) or atomic time, UTC (in which case 8 hours must >be added on before displaying the time to the user).
Correct. >There is no right or wrong answer to which method to use. Linux assumes >the hardware uses UTC, Windows assumes it uses local time. Both can be >configured to use either method >(https://wiki.archlinux.org/index.php/Time#Time_standard) and it's best >if they agree. 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 system without the limitations of DOS, there is no good reason to perpetuate the crap this way: store UTC and leave the clock alone. -- Steve McIntyre, Cambridge, UK. st...@einval.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1uphff-0007hx...@mail.einval.com
