Bug#408954: checkroot.sh: should not skip running fsck with JFS root

Dmitry Bogatov KAction at debian.org
Wed Mar 6 14:36:09 GMT 2019

[2019-03-02 00:01] Pierre Ynard <linkfanel at yahoo.fr>
> Do we want a blacklist, or a whitelist?
> Do we want to delegate conditionality to particular implementations? If
> so, which factors? Running on battery was suggested. Shipping a dummy
> fsck.$type is a way to delegate the possibility or impossibility to fsck
> to the implementation - but that doesn't seem like the best or most
> flexible technical solution to me.

If you ask me, requiring every FS to provide /usr/bin/fsck.$FS and
standartizing command line options is good thing. This would eliminate
both whitelist and blacklist.

What more important, it would remove assumption, that maintainers of
initscripts have in-depth understanding of all file systems in

> What is the difference between checking the root filesystem, and
> checking other filesystems? Why would the logic to skip brtfs and nfs
> apply only to checkroot.sh, why would checkroot.sh ignore FSCKTYPES?

No idea, sorry.

> Can we have a switch in fsck similar to -A to let it parse the pass
> field of /etc/fstab for us, except when checking only one device
> passed in argument, or only the root fs? That way we wouldn't have
> to parse it ourselves too just for the root fs and pass it from
> /lib/init/mount-functions.sh back to /etc/init.d/checkroot.sh.

We can write such universal front-end, don't we?
        Note, that I send and fetch email in batch, once every 24 hours.
                 If matter is urgent, try https://t.me/kaction

More information about the Debian-init-diversity mailing list