bug #501801 and #562898 seem to be related mountall bugs
** Also affects: mountall (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mountall (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: util-linux (Ubuntu Lucid)
Importance: Undecided
setting to high and milestoning for lucid since that renders many armel
installations unbootable
** Changed in: mountall (Ubuntu Lucid)
Importance: Undecided = High
** Changed in: util-linux (Ubuntu Lucid)
Importance: Undecided = High
** Changed in: mountall (Ubuntu Lucid)
Milestone:
Beagleboard has no RTC backup battery. Though one can be soldered on,
most devices won't have any.
So we need fsck to skip the time check.
** Changed in: util-linux (Ubuntu Lucid)
Status: New = Confirmed
** Changed in: mountall (Ubuntu Lucid)
Status: New = Confirmed
--
there is
Just adding some OMAP Board Details.
Development Boards:
Original Bx/C2 Beagles have no prevision for installing a backup battery.
C3 C4(current shipping) Beagles have an area reserved for end users to
solder a 3V coin battery. I believe the XM will have the same
provision, i just don't have
Robert: that's not a nasty hack - that's the canon way to work around
this issue - this should be identical to just doing:
[options]
broken_system_clock = true
which will set preen_ok for those two problems
--
there is no way to tell fsck to ignore broken clocks on embedded systems
This is not a mountall issue, if e2fsck's broken_system_clock=true
option is not working, that's an e2fsck bug
** Changed in: mountall (Ubuntu Lucid)
Status: Confirmed = Invalid
--
there is no way to tell fsck to ignore broken clocks on embedded systems
fwiw, here's the e2fsck code for broken_system_clock, so it really
should be directly equivalent!
if ((code == PR_0_FUTURE_SB_LAST_MOUNT) ||
(code == PR_0_FUTURE_SB_LAST_WRITE)) {
profile_get_boolean(ctx-profile, options,
Having chatted to ogra, we think that broken_system_clock and that
config snippet are both working fine.
The problem is that this results in a fix to the root filesystem, and
that in turn results in the requirement that we reboot (the mounted root
fs has changed!)
And rebooting clears the
