Add back persistance fsck option
Commit bc79205b removed the fsck option due to lack of usage. But it can be useful and we have had customer escalations due to corrupted persistent filesystem, which are solved by being able to configure this option.
Mailing list thread: https://lists.debian.org/debian-live/2015/08/msg00107.html
Merge request reports
Activity
Hum, all those environment variables have been added recently. But I missed this detail when I reviewed the patch from @bdrung that I merged in 83882947.
I think we should be consistent and use true/false everywhere, also in those recently-added environment variables.
But we should really recognize "true" and "yes" as true values (and "false" / "no" as false values). "y" or "n" is not consistent with what is done in live-config or live-build.
I am fine with fixing 83882947 to use "true" and "yes" for consistency.
assigned to @hertzog
added 1 commit
- 49930473 - Use true|false instead of y|n for environment variables
- Resolved by Luca Boccassi