Thom and I discussed this at the recent conference, and I believe we decided
that #2 is the way to go.
Also, it would be nice if e2fsck would exit successfully (and simply skip
updating the mount count or last-checked data in the superblock) if the user
interrupted it. This would allow the scheduled checks to be gracefully skipped.
Thom and I discussed this at the recent conference, and I believe we decided
that #2 is the way to go.
Also, it would be nice if e2fsck would exit successfully (and simply skip
updating the mount count or last-checked data in the superblock) if the user
interrupted it. This would allow the scheduled checks to be gracefully skipped.