https://bugzilla.novell.com/show_bug.cgi?id=753932 https://bugzilla.novell.com/show_bug.cgi?id=753932#c7 --- Comment #7 from jorge aires <jorge.adriano@gmail.com> 2012-06-22 19:23:13 UTC --- (In reply to comment #5)
To be short:
The clock of linux kernel has to be in UTC The linux kernel reads its initial clock value from CMOS
If CMOS is not in UTC the kernel has to told about to be able to switch back to real UTC
This is done before the root file system from the first disk is touched otherwise the file system is not in a clean state due wrong time stamps
Last two points are done in the initial ram disk which is also used to check and mount the root file system and start the initial program (systemd/sysvinit)
it might be technical and sounds complicated but this is how it is and if you run into trouble at installation time this has to be fixed in the installation routines
Thanks for your explanation. It's quite clear. Don't get me wrong, I understand that things are the way they are, and there's nothing we can do about that. All I meant is that this complexity should be hidden from users in general, who shouldn't have to face it. If the CMOS clock is UTC by default, and that's what the clock of the linux kernel expects, that's how things should work unless the user goes out of his way to specify some other settings. My guess (and I may be wrong!) is that during installation, at some step, we're asked for what appears to be a timezone, which sets the clock to local time. And, if I am right, and this is what causes all the problems, it really shouldn't be this easy to mess the settings up. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.