Re: [opensuse] opensuse 11.0 x64 time messed up with dual boot
- From: James Knott <james.knott@xxxxxxxxxx>
- Date: Fri, 08 Aug 2008 13:17:21 -0400
Vahe Avedissian wrote:
Linux can be configured to set the hardware clock to either local or UTC time, though all Linux/Unix time stamps are UTC and then converted to local time. I don't know if it still occurs, but years ago, when logging into a Windows domain in a different time zone would change your computer's time. Such a thing wouldn't happen in Linux, where everything works in UTC.
Hummm... Not surprised our friends in Redmond had something to do with this...
The workaround/solution is simply enough. My question is, whenever I need to boot M$N and
then boot back to opensuse, I go to yast ->date/time and re-sync up with the UTC. Sometimes,
I forget to do that and should I do an update with YOU, it *really* messes up the zypper database
and what packages need to be updated, etc...
My question is, why does the clock not get re-synced to the UTC at boot time? I could add a couple of
lines in the startup scripts to do so, but you'd think that should be automatic. Does that make sense?
Vahe
You shouldn't have to go into Yast on booting back into Linux. Simply configure Linux so the hardware clock is local. Then configure Windows so that it won't change the clock for DST. All should be good now.
--
Use OpenOffice.org <http://www.openoffice.org>
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
- References:
- Re: [opensuse] opensuse 11.0 x64 time messed up with dual boot
- From: Vahe Avedissian
- Re: [opensuse] opensuse 11.0 x64 time messed up with dual boot
- Prev by Date: Re: [opensuse] Sending email with telnet on port 25
- Next by Date: RE: [opensuse] Rdesktop crashing after updates
- Previous by thread: Re: [opensuse] opensuse 11.0 x64 time messed up with dual boot
- Next by thread: Re: [opensuse] opensuse 11.0 x64 time messed up with dual boot
- Index(es):
Relevant Pages
|