On Tue, 03 Jan 2006, Brandon Simmons wrote: > boot. According to the Debian changelog for the e2fsprogs package, the newest > version checks for this, so I don't know whether e2fsprogs is mistaken or > whether there really is a problem. How would I go about checking this?
Short and to the point: stop using your RTC in local timezone mode. Currently it simply cannot be as well supported as a RTC in UTC mode, and it was never a sound engineering idea to begin with to have that in local time, even back on the DOS days it was already broken by design. Real fix: whatever you do, make sure /etc/localtime IS IN THE ROOT FILESYSTEM (it is usually a symlink to /usr, and since you got the bug, your /usr is probably a separate partition...). Cosmetic fix: Edit hwclockfirst.sh and add right at the top of the file TZ=TMP+200 (if your timezone is two hours less than UTC) or TZ=ABC-500 (if it is five hours more than UTC). Move hwclock.sh in /etc/rcS.d to priority 36. Forget about getting it right for daylight savings, leap seconds and any other advanced timezone stuff until after S35mountall has run, you'll have to update that TZ= thing manually... See tzset(3) for more information on TZ. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342887 for more details. Note that glibc will have to change how they deal with /etc/localtime for a proper fix to this one. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
