There are a few remaining issues with fsck in the initramfs that I'd
like to get cleaned up for jessie.
The fsck log file is not documented nor particularly discoverable. I
think this may be the root of #780352, but don't know for sure.
There is the problem of running e2fsck when the system time is set
wrongly thanks to an RTC in local time (#767040). That particular bug
is now assigned to an installer component, clock-setup, which I've
changed to create the necessary configuration file. So new installs
should be good, but upgrades still require manual reconfiguration.
Bug #767040 is exacerbated by the fact that both the initramfs and the
real init system run fsck on the root filesystem. There was some
discussion on that bug of coordinating with the real init system to
avoid duplicate fsck's. So this adds creation of stamp files that can
be used to make fsck conditional in the real init system.
Ben.
Ben Hutchings (3):
Add '.log' to fsck log output file, and document its existence
(Closes: #780352)
Remove old comment about running shell on failure of fsck
Create stamp files to tell the real init system fsck was successful
(Closes: #??????)
initramfs-tools.8 | 12 ++++++++++++
scripts/functions | 8 ++++----
2 files changed, 16 insertions(+), 4 deletions(-)
--
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett
Attachment:
signature.asc
Description: This is a digitally signed message part