Am 08.04.2015 um 12:27 schrieb Lennart Poettering:
Well, the routine check is only done by Ubuntu/Debian, it is not enabled on any enterprise distro or on Fedora. Maybe Ubuntu/Debian should also turn this off? Note that the routine check is not different than a normal check really, it just is triggered by a mount counter instead of a dirty flag, that's all. Hence it makes little difference what you cancel, both is dangerous, and a bad idea to allow unauthenticated. Also, to my knowledge plymouth on Ubuntu never showed a different UI for both cases, did it? How is the admin supposed to know when it is just dangerous to cancel the fsck (in your "routine" check case), and when it is extra dangerous (in the non-"routine" check case)? Maybe the right fix for Ubuntu is to stop enabling the "routine" check logic?
why would you want to disable it?short before christmas i had a faulty ext4 FS needing even manual confirmation of repairs - i don't think it's a good idea to not trigger that automatically and frankly it *should have been* triggered that way
https://bugzilla.redhat.com/show_bug.cgi?id=1105877
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
