touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #84831
[Bug 563618] Re: Ignoring a broken clock results in infinite reboots; not ignoring results in fsck failure; no solution to this problem
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: e2fsprogs (Ubuntu Lucid)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/563618
Title:
Ignoring a broken clock results in infinite reboots; not ignoring
results in fsck failure; no solution to this problem
Status in e2fsprogs:
Unknown
Status in e2fsprogs package in Ubuntu:
New
Status in flash-kernel package in Ubuntu:
Fix Released
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in mountall package in Ubuntu:
Invalid
Status in e2fsprogs source package in Lucid:
Won't Fix
Status in flash-kernel source package in Lucid:
Fix Released
Status in initramfs-tools source package in Lucid:
Fix Released
Status in mountall source package in Lucid:
Invalid
Bug description:
Binary package hint: util-linux
while e2fsck has the optioon to add an e2fsck.conf with an option to
ignore broken system clocks, fsck does not have the ability to
override this.
that behavior together with a mountall bug which does not give the
user a maintenance shell when fsck exits but makes it go into an
endless loop renders many ARM platforms we support unbootable (we have
several development boards that either come with an unloaded (imx51)
or without battery at all (omap beagleboard)).
the only workaround in this case is to edit both fstab files on the
rootfs (/etc/fstab and /lib/init/fstab) and change the pass number for
the root filesystem from 1 to 0
To manage notifications about this bug go to:
https://bugs.launchpad.net/e2fsprogs/+bug/563618/+subscriptions