Bug#343645: Processed: Re: [Pkg-sysvinit-devel] Processed: Re: Bug#343645: e2fsprogs: Superblock last mount time is in the future, fix it ? (Y)

Henrique de Moraes Holschuh hmh at debian.org
Fri Jan 6 11:29:02 UTC 2006

On Fri, 06 Jan 2006, Thomas Dickey wrote:
> On Thu, Jan 05, 2006 at 04:50:24PM +0100, Henrique de Moraes Holschuh wrote:
> > I was trying to write one that did all in util-linux, but during that time
> > it become apparent that the fix needs to involve glibc and initscripts too
> > to be effective during DST.
> The patch was too simplistic to be of use anyway.  Granted that it was
> "tested lightly"...

Simplistic as in?  What did it fail to do?

The whole fix involves a lot of crap that won't be done by util-linux, but
rather initscripts.  The patch just fixes util-linux back to what it should
be doing.

> I don't see any discussion on this thread that points out that modifying
> the hardware clock from another system can make the Debian system unbootable
> (until one waits for the future to arrive ;-).

And you won't :-P  We don't protect people from hanging themselves on
purpose.  If you want to discuss that the test is completely stupid, or that
fsck is not repairing it correctly or in the desired way, you have to talk
to the e2fsck maintainer.

OTOH, a misshandled clock (as in we say we support it in local time but
really don't) is a bug no matter how we look at it, so even if e2fsck stops
caring about the system clock, we would still need to do something about
this issue at early boot anyway.  Or drop the non-UTC support for the RTC.

  "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

More information about the Pkg-sysvinit-devel mailing list