Bug 569335
Summary: | dracut doesn't know whether hwclock is utc or localtime | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | JW <ohtmvyyn> |
Component: | udev | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | harald, jonathan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | udev-151-7.fc13 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-25 22:36:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
JW
2010-03-01 10:46:37 UTC
Actually the same applies to the real root, as long as the rules in /lib/udev/rules.d/88-clock.rules are not yet triggered, AFAIK. I should also mention that for a lot of people WEST of UTC this isn't much of a problem. All of the files in /dev will look slightly older than they should be (eg. 5hr old if you are in NY), and no program will complain about that. But if you are EAST of UTC then there will be a problem because the times of the device files will be set at some time into the future (like 10hrs ahead in Australia) and programs will certainly complain about that. Also, my system doesn't have a 88-clock.rules. Where does that come from? Can you do a "rpm -qif" on that? $ rpm -qf /lib/udev/rules.d/88-clock.rules initscripts-9.02.1-1.x86_64 In any case whatever is in 88-clock.rules is irrelevant because /dev has already been populated with device files created in the future during the boot sequence. I would move a general "touch" to /sbin/start_udev (called by rc.sysinit) to be executed after the udev trigger. udev-145-16.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/udev-145-16.fc12 udev-151-7.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/udev-151-7.fc13 udev-151-7.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update udev'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/udev-151-7.fc13 udev-145-19.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update udev'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/udev-145-19.fc12 udev-145-19.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. udev-151-7.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |