On Sat, Nov 14, 2009 at 02:32:54AM +0100, Eugeniy Meshcheryakov wrote:
> 13 листопада 2009 о 19:43 -0500 Theodore Tso написав(-ла):
> > (1) I'm the maintainer. (2) The bug doesn't even vaguely fit the
> > definition of "grave":
> >
> > makes the package in question unusable or mostly so, or causes
> > data loss, or introduces a security hole allowing access to the
> > accounts of users who use the package
> This bug however makes some systems unusable for no good reason.
> And it does not look like a hard to fix bug at all.
There are a number of workarounds. One is to take the kernel patch
(or upgrading to 2.6.32, which will have the fix). Or you can fix
your system clock to tick GMT, as opposed to localtime, which is
fraught with all sorts of problems, especially around the transition
in and out of summer-time/daylight savings time. Or you add the
following stanza to /etc/e2fsck.conf:
[options]
buggy_init_scripts = 1
One could just as easily argue that the real bug is having the
hardware CMOS time tick in localtime. Granted we should make the
system more robust against people who incorrectly set their system
clock to be bug-for-bug compatible with Microsoft, but in no way does
this justify increasing the severity to "grave".
In fact we do have changes pending in e2fsprogs and in the kernel to
make things more robust against brain-damaged configurations. See
commit ba5131f6 in the e2fsprogs maint branch. Until these changes
find their way into Debian packages, my recommendation is to either
(a) fix your hardware clock to tick UTC time, or (b) apply the
buggy_init_scripts workaround to /etc/e2fsck.conf.
- Ted
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
