Although 588 is titled as 'system-config-date not writing back to the hw', but isn't 588 final result (workaround) fixing e2fsprogs to make fsck tolerance timestamp checking? Please see the several last comments and solutions.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Clark, Joel Sent: Thursday, July 01, 2010 1:31 AM To: Arjan van de Ven; Development for the MeeGo Project (discussion list) Cc: Foster, Susan B; Girr, Paul Subject: Re: [MeeGo-dev] meego boot menu I searched bugs.meego.com for a e2fsprogs bug, but I can't find it. Any idea when the e2fsprogs fix was made? regards Joel -----Original Message----- From: Arjan van de Ven [mailto:[email protected]] Sent: Wednesday, June 30, 2010 9:37 AM To: Development for the MeeGo Project (discussion list) Cc: Clark, Joel; Picard, Tom S; Girr, Paul; Foster, Susan B; Branch, Brett Subject: Re: [MeeGo-dev] meego boot menu On 6/30/2010 9:26 AM, Clark, Joel wrote: > > Arjan, > > Do you know if BMC#588 affected all devices or just Netbook? Was it a > core issue? If yes, what was the core fix? > 588 is about system-config-date not writing back to the hw. we had a different bug where ext3 fsck went into throwing fits like a 3 year old when the current date and the filesystem dates where waaay out of whack. We fixed that in the e2fsprogs package for fsck to be more tolerant to this situation. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
