From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) Description of problem: When installing a new OS, we get the opportunity to select what time zone will be used. We do not get a chance to change the PC's clock. This means that all the dates/times on all the installed files are wrong. This causes quite a lot of problems if the PC has been shipped "back a time zone", since when the OS finally boots and asks us for the time, all the files in the OS end up having time stamps in the future. Version-Release number of selected component (if applicable): ES4 update 2 How reproducible: Always Steps to Reproduce: 1. Get a PC with the clock set right in your own time zone 2. Install using some other zone Actual Results: wrong times on most files Expected Results: correct times Additional info:
We already do this in firstboot. It seems like we could just move the code back into anaconda and set it there. However, we're probably not going to be able to put this into a RHEL update release.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fixing version to align with rawhide again. Sorry for the noise.
This needs to happen in anaconda not firstboot. Otherwise the installed mtimes can still be all back to the future. I'm compulsive about putting these two lines into kickstart %pre: rdate -s [rfc868-server1] [rfc868-server2] [rfc868-server3] hwclock -w However, only a few public ntp servers such as time.nist.gov support the coarse rdate/time protocol.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I am unlikely to get to this any time soon, so reassigning back to anaconda-maint-list in case someone else has free time and an itch. It's going to get buried being assigned to me.
I'm not sure whether moving the time dialog from bootloader would a good change. Chris, were you planning to implement this? Chris, Jon and Curtis: isn't it possible in these cases for you to setup the time in BIOS before the computer boots? Unless I am convinced this is really useful, I am planning to close this as won't fix. Ales
Ales - yes, it can be useful as in some cases, the system can end up with files with times later than the actual time, and the boot process will complain about that. I was always planning on going back and looking at our timezone screen again to see how (1) it could be brought more in line with what s-c-date does, and (2) we could work in a time setting widget.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The newui in anaconda-18.3 includes this functionality.