The Humax binary that does the on-screen disk format calls functions from
/usr/lib/libext2fs.so.2
(actually .2.4), so they basically implemented their own mke2fs. One can imagine how horlickingly well that went: well enough not to block shipping, but no better. The same library is invoked indirectly by the disk maintenance utilities in
/sbin
, but we can choose the parameters when running them.
However the filesystem checks seem to be done by running fsck, judging by these strings in the binary (
-p
for startup check,
-f -y
for manually initiated):
Code:
e2fsck -F -j ext3 -p %s
e2fsck -F -j ext3 -f -y %s
The CF
libext2fs.so.2.4
contains version string 1.41.11. A more recent build of e2fsprogs (eg 1.42.13) is available as a package but wouldn't normally be available in Maintenance Mode. The package versions build monolithic programs with no libext2fs.
Strangely there are actual duplicates of all the CF e2fsprogs libraries from
/usr/lib
in
/usr/lib/ext
. The firmware programs all seem to be bound to the
/usr/lib
versions, including the main programs in
/usr/lib/ext/bin
that are invoked from the
/sbin
scripts. A chance to get 600kB back in CF ?3.15? with some straightforward hard-linking (I wondered:
stat shows no extra links)?