[2019-03-09 21:57] Thorsten Glaser <t.gla...@tarent.de>
> > But I really want to have some transition plan to get rid of
> > /forcecheck, something like:
>
> … you might like that tune2fs can now (1.45.0-1, not yet in
> buster, officially not likely to make it but we can hope) set
> a flag force_fsck that next boot’s auto e2fsck will honour.
> I’m assuming this works for ext2/ext3/ext4; ask tytso if unsure.
>
> So just print a warning (in the first upload after buster) and
> recommend using that instead, *AND* document in /usr/share/doc/…/
> that the file should not be used any more, and get the reiserfs
> people (and others) to invent something similar. It’s more granular
> (per filesystem) and thus better anyway.
So, you propose that we:
* drop all checks for /forcecheck
* document this fact in NEWS file
* write documentation, that e[2-4]fs users should use tune2fs tool
instead
Well, fine, but what about reiserfs and minix? And, I can't see
standalone tune2fs even in unstable:
$ apt-file find /bin/tune2fs
android-sdk: /usr/lib/android-sdk/tools/bin/tune2fs
--
Note, that I send and fetch email in batch, once every 24 hours.
If matter is urgent, try https://t.me/kaction
--
